lunar-walker opened a new issue, #11447:
URL: https://github.com/apache/tvm/issues/11447

   Hello,
   I'm trying to compile latest tvm on Windows 10 / Visual Studio Community 
2019 with USE_CUDA, USE_LLVM "llvm-config --link-static", USE MKL, USE_MKLDNN, 
USE_CUDNN, USE_DNNL_CODEGEN, USE_TENSORRT_CODEGEN, USE_TENSORRT_RUNTIME options 
(cmake generate solution files successfully without any error) but it failed 
with following:-
   
   2>D:\code\tvm\src\runtime\contrib\dnnl\dnnl_json_runtime.cc(609,18): error 
C2131: expression did not evaluate to a constant
   2>D:\code\tvm\src\runtime\contrib\dnnl\dnnl_json_runtime.cc(609,18): message 
: failure was caused by a read of a variable outside its lifetime
   2>D:\code\tvm\src\runtime\contrib\dnnl\dnnl_json_runtime.cc(609,18): message 
: see usage of 'OC'
   
   Then later a lot of link errors.... i.e.
   4>LINK : fatal error LNK1181: cannot open input file 
'D:\code\tvm\build\tvm_runtime_objs.dir\Release\src\runtime\vm\vm.cc.obj'
   8>LINK : warning LNK4044: unrecognized option '/Wl,--exclude-libs,ALL'; 
ignored
   7>LINK : warning LNK4044: unrecognized option '/Wl,--exclude-libs,ALL'; 
ignored
   8>LINK : fatal error LNK1181: cannot open input file 
'D:\code\tvm\build\tvm_objs.dir\Release\src\relay\backend\contrib\tensorrt\codegen.cc.obj'
   7>LINK : fatal error LNK1181: cannot open input file 
'D:\code\tvm\build\tvm_objs.dir\Release\src\relay\backend\contrib\tensorrt\codegen.cc.obj'
   
   I don't know much of C++ but apparently error 'expression did not evaluate 
to a constant' in \src\runtime\contrib\dnnl\dnnl_json_runtime.cc line 609 is 
justified as on same line  float bias[OC] = {0}; OC is not constant which 
compiler expects at compile time.
   
   If respective developer of the dnnl codegen module can look into it?
   
   Thanks for all the great work.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to