https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100293
--- Comment #3 from Brecht Sanders <brechtsanders at users dot sourceforge.net> --- My bad, yes I was using nvptx-tools (master from https://github.com/MentorEmbedded/nvptx-tools). my configure command for nvptx offload engine looks like this ./configure --prefix=/R/winlibs64_stage/inst_gcc-offload-nvptx-11.1.0/share/gcc --build=x86_64-w64-mingw32 --host=x86_64-w64-mingw32 --target=nvptx-none --enable-as-accelerator-for=x86_64-w64-mingw32 --with-build-time-tools=/d/Prog/winlibs64_stage/custombuilt/share/nvptx-tools/nvptx-none/bin --with-gnu-as --with-gnu-ld --disable-serial-configure --enable-checking=release --without-libbacktrace --without-included-gettext --without-cuda-driver --enable-multiarch --enable-newlib-io-long-long --enable-linker-build-id --enable-multilib --disable-sjlj-exceptions --disable-libunwind-exceptions --disable-libgomp --enable-languages=c,c++,lto,objc,obj-c++,d So yes, --disable-sjlj-exceptions --enable-newlib-io-long-long is there. Note that the same build scripts worked fine with GCC 10.3.0 and older.
