https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119369
--- Comment #6 from Thomas Schwinge <tschwinge at gcc dot gnu.org> --- (In reply to Andrew Stubbs from comment #5) > However, given that weak symbols are known to be half-broken then maybe > -fno-weak is the correct solution in that configuration? I'd prefer to not do that, as that would complicate other things: GCC/C++ likes using weak definitions a lot, and these work fine with both GCC/GCN and GCC/nvptx. (Just weak undefined symbols are problematic -- for both.) I'll be happy to later on (help) look into the ideas we discussed, but until then, OK to push <https://inbox.sourceware.org/20250331094849.400700-2-tschwi...@baylibre.com> "GCN: Don't emit weak undefined symbols [PR119369]"? (Jonathan already approved <https://inbox.sourceware.org/20250331094849.400700-1-tschwi...@baylibre.com> "GCN, libstdc++: '#define _GLIBCXX_USE_WEAK_REF 0' [PR119369]"; I suppose you won't object to that one either?)
