https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123730
--- Comment #3 from Thomas Schwinge <tschwinge at gcc dot gnu.org> --- (In reply to Andrew Pinski from comment #1) > How does nvptx handle lto? It doesn't, currently. ;-) (In reply to Andrew Pinski from comment #2) > > as other front ends are doing, if I remember correctly > > Go uses a similar as algol68 here I thought that GCC/Go uses '[...].gox' files for export information (..., and GCC/Rust copied that: '[...].rox' files?), but, indeed, I see 'gcc/go/go-backend.cc-go_write_export_data' looks very similar to 'gcc/algol68/a68-exports.cc:a68_switch_to_export_section'. > but I doubt nvptx is supported. But at least GCC/nvptx with '--enable-languages=all' can build GCC/Go (etc.). (..., and run their test suites -- with very mixed results, indeed.)
