You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
nvrtc.nvrtcCompileProgram is changing the preferred encoding from UTF-8 to ANSI_X3.4-1968 #29
Just to give a small update. By discussing the issue with Nvidia we found out that it is possible to export LC_ALL="POSIX" as a workaround to avoid NVCC changing the encoding to ASCII.
The causes of the bug are still unknown and I will report when I have any other news.
Just to give a small update. By discussing the issue with Nvidia we found out that it is possible to export LC_ALL="POSIX" as a workaround to avoid NVCC changing the encoding to ASCII.
The causes of the bug are still unknown and I will report when I have any other news.
Any updates here? It is indeed a bug in NVRTC, specifically nvrtcCompileProgram and can be reproduced in C++:
I'm a bit confused about the statement "export LC_ALL="POSIX" as a workaround to avoid NVCC changing the encoding to ASCII" as that by definition sets the encoding to ASCII in the first place. So the change is only masked.
We are glad to let you know our compiler team has fixed the issue . nvrtc will no longer change user program locale/encoding . This fix will aim a future CUDA 12.x release around September 2024 . Feel free to comment back here if you need help in confirming a bug fix version in the future.
However, the bug is still open. So I don't know if it was fixed yet.
@redsnic thank you! From what I have seen elsewhere; the fix was indeed pushed, but only targets CUDA 12.7+. In the meantime, using Python in UTF-8 mode allows bypassing it (the locale is still changed, but Python doesn't take it into account.
Activity
kmaehashi commentedon Oct 15, 2022
This sounds like an issue of NVRTC rather than CUDA Python. The issue was also reproducible in CuPy built without CUDA Python.
Env: CUDA 11.8 / Ubuntu 20.04
redsnic commentedon Oct 15, 2022
Good to know, I have filed a bug to Nvidia now, let's see.
Thank you again.
redsnic commentedon Oct 27, 2022
Just to give a small update. By discussing the issue with Nvidia we found out that it is possible to
export LC_ALL="POSIX"as a workaround to avoid NVCC changing the encoding to ASCII.The causes of the bug are still unknown and I will report when I have any other news.
vzhurba01 commentedon Dec 5, 2022
Since this is a bug outside of CUDA Python, I'll close this issue.
Thanks for sharing that workaround. If there's a link you can share for where this bug is being tracked, I'm sure folks would appreciate it.
redsnic commentedon Dec 6, 2022
Here is the link to the bug report: https://developer.nvidia.com/nvidia_bug/3833924
Thank you again for your help
Fixes #625, which is due to a bug caused by NVIDIA (NVIDIA/cuda-pytho…
Explicit file encoding for cuda mixed environment due to issue NVIDIA…
Explicit file encoding for cuda mixed environment due to issue NVIDIA…
Flamefire commentedon Mar 7, 2024
Any updates here? It is indeed a bug in NVRTC, specifically
nvrtcCompileProgramand can be reproduced in C++:Compile with
nvcc test.cu -lnvrtcand observe:I'm a bit confused about the statement "
export LC_ALL="POSIX"as a workaround to avoid NVCC changing the encoding to ASCII" as that by definition sets the encoding to ASCII in the first place. So the change is only masked.Explicit file encoding for cuda mixed environment due to issue NVIDIA…
LoicGrobol commentedon Feb 17, 2025
@redsnic Any news about this? The upstream bug report seems to be access-restricted?
redsnic commentedon Feb 24, 2025
Sorry for the late reply.
This was the last update:
We are glad to let you know our compiler team has fixed the issue . nvrtc will no longer change user program locale/encoding . This fix will aim a future CUDA 12.x release around September 2024 . Feel free to comment back here if you need help in confirming a bug fix version in the future.
However, the bug is still open. So I don't know if it was fixed yet.
LoicGrobol commentedon Feb 24, 2025
@redsnic thank you! From what I have seen elsewhere; the fix was indeed pushed, but only targets CUDA 12.7+. In the meantime, using Python in UTF-8 mode allows bypassing it (the locale is still changed, but Python doesn't take it into account.
Merging EE-ADC code (#38)
Molecular ADC for electronic excitations (EE-ADC) (#2893)
Merging EE-ADC code (#38)