nvcc fatal : Value 'c++17' is not defined for option 'std'

Question

Vyacheslav Samokhvalov 2021-6-23

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/863035-nvcc-fatal-value-c-17-is-not-defined-for-option-std

评论： Joss Knight 2021-6-24

Hello,

I'm would like to use some C++17 features in my library. The library is header only, and compiles with MSVC 15.19 v14.16 toolset and CUDA 11.3 that are installed on my machine. I wrap this library in a mex function which acts as an interface for inputs and outputs from and to Matlab, but having trouble compiling it.

I use the following command to compile:

mexcuda -v -R2018a '-LC:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.3\lib\x64' -lcublas ...
    NVCC_FLAGS='-std=c++17 -Xcompiler=/std:c++17 --default-stream legacy'...
    .\path\to\mex\file.cu

and get:

Error using mex
nvcc fatal   : Value 'c++17' is not defined for option 'std'

In the nvcc_msvcpp2017.xml build configuration file I noticed that CUDA 10.1 is referenced. This version indeed does not support C++17 standard, but I find it bizzare that anything would compile at all seing as I do not have CUDA 10.1 installed on my system (unless it shipped with Matlab). I tried creating a custom .xml file to correct the versioning but that did not solve the issue, my guess though is that I need to adjust some environment variable, but I have no clue which one.

Thank for your help!

1 个评论
显示 -1更早的评论隐藏 -1更早的评论

Joss Knight 2021-6-24

"I find it bizzare that anything would compile at all seing as I do not have CUDA 10.1 installed on my system (unless it shipped with Matlab)"

It is! From the doc:

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Linda Koletsou Soulti 2021-6-23

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/863035-nvcc-fatal-value-c-17-is-not-defined-for-option-std#answer_731575

在 MATLAB Online 中打开

Hello Vyacheslav,

In order to specify the location of NVCC on your system for MEXCUDA to use, you should execute the following command:

setenv('MW_NVCC_PATH','/path/to/your/nvcc');

The version of the CUDA Toolkit that you can safely use, is the one supported by your MATLAB release. You can find more information on that along with the compatible version of the CUDA Toolkit for your release on the following link:

https://www.mathworks.com/help/parallel-computing/gpu-support-by-release.html#mw_8f38487a-b465-4cd8-8e01-063f1f8c9e6e

Cheers,

Linda

2 个评论
显示无隐藏无

Vyacheslav Samokhvalov 2021-6-24

编辑：Vyacheslav Samokhvalov 2021-6-24

在 MATLAB Online 中打开

It seems that setting

setenv('MW_NVCC_PATH','/path/to/your/nvcc');

makes no difference. It looks like MATLAB Parallel Toolbox ships CUDA 10.1. Looking at lines 220-223 in nvcc_msvcpp2017.xml mex configuration file, the PATH variable concatenates

PATH="$MATLABROOT\sys\cuda\$ARCH\cuda\nvvm\bin;$MATLABROOT\sys\cuda\$ARCH\cuda\bin"

Idem for LIB with

LIB="$MATLABROOT\sys\cuda\$ARCH\cuda\lib\x64"

This means that even if I have a newer version of CUDA installed on my machine, despite the setting in MW_NVCC_PATH, CUDA 10.1 shipped with MATLAB is used to compile the code. The argument -LC:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.3\lib\x64 to link CUBLAS from a newer version of CUDA produced no errors, because CUBLAS from $MATLABROOT\sys\cuda\$ARCH\cuda\lib\x64 was linked to instead.

Linda Koletsou Soulti 2021-6-24

Hello Vyacheslav,

We do not support using a different version of the CUDA Toolkit than the one supported by your version of MATLAB. It seems that the version of MATLAB you use supports the CUDA Toolkit version 10.1.

You can find more information about the compatible version of the CUDA Toolkit for each release on the following link:

https://www.mathworks.com/help/parallel-computing/gpu-support-by-release.html#mw_8f38487a-b465-4cd8-8e01-063f1f8c9e6e

Cheers,

Linda

请先登录，再进行评论。