dmlc / dmlc/MXNet.cpp

get error when run charRNN with vs2013update5

Open
#60 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
115
Forks
78
PR merge metrics
No merged PRs in 30d

Description

```
1>..\..\..\example\charRNN.cpp(101): error C2661: 'mxnet::cpp::transpose' : no overloaded function takes 1 arguments
1>..\..\..\example\charRNN.cpp(149): warning C4267: 'initializing' : conversion from 'size_t' to 'int', possible loss of data
1>..\..\..\example\charRNN.cpp(153): warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of data
1>..\..\..\example\charRNN.cpp(202): warning C4267: 'return' : conversion from 'size_t' to 'int', possible loss of data
1>..\..\..\example\charRNN.cpp(288): error C2664: 'std::tuple,std::equal_to<_Kty>,std::allocator>>,std::vector>>::tuple(const std::tuple,std::equal_to<_Kty>,std::allocator>>,std::vector>> &)' : cannot convert argument 1 from 'std::unordered_map,std::equal_to<_Kty>,std::allocator>>' to 'std::allocator_arg_t'
1> with
1> [
1> _Kty=wchar_t
1> , _Ty=mx_float
1> ]
1> No user-defined-conversion operator available that can perform this conversion, or the operator cannot be called
1>..\..\..\example\charRNN.cpp(349): warning C4305: 'initializing' : truncation from 'double' to 'mx_float'
1>..\..\..\example\charRNN.cpp(372): warning C4305: 'argument' : truncation from 'double' to 'float'
1>..\..\..\example\charRNN.cpp(376): warning C4305: 'initializing' : truncation from 'double' to 'mx_float'
1>..\..\..\example\charRNN.cpp(377): warning C4305: 'initializing' : truncation from 'double' to 'mx_float'
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

```

maybe the transpose op should add a arg about axes?
how can fixed it?

or maybe vs2015 don't have this problem...?
but i can't find a transpose function with only one arg exactly

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.