https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97070
--- Comment #5 from Ioannis E. Venetis ---
I am sorry for coming back to this and for the confusion, but my previous
report of having solved the problem proved wrong.
I was getting the correct result because the code was running on the CPU, not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97070
--- Comment #4 from Ioannis E. Venetis ---
It seems that the problem was indeed some kind of confusion due to multiple gcc
installs. I removed the nvptx related packages of gcc-9.3.0 from my Ubuntu
16.04.7 LTS system (packages
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97070
--- Comment #3 from Ioannis E. Venetis ---
This is weird. Just downloaded gcc from git and built version 11.0
$ /home/venetis/apps/gcc-20200928/bin/gcc -v
Using built-in specs.
COLLECT_GCC=/home/venetis/apps/gcc-20200928/bin/gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97070
--- Comment #2 from Ioannis E. Venetis ---
Created attachment 49279
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49279=edit
GCC building script
