https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89856
--- Comment #1 from Daniel Vollmer <zerolo at gmail dot com> --- Initial analysis from Iain Sandoe > OK (initial analysis). what we have is > > __ZGVZ19BroadcastFromMasterImEvPT_mE4bufs: > .space 8 > .... > > LPX0: > .... > > and then a reference to LPX0 in __GLOBAL__sub_I_65535_0_test.cpp. > > So ld64 breaks the code and data into "atoms" where each atom begins with a > linker-visible symbol. > > What it's saying is that the data pointed to by LPX0 is in the atom named > __ZGVZ19BroadcastFromMasterImEvPT_mE4bufs (because LPX0 is not visible to > the linker). > > right now, not sure if it's really a potential issue or just more linker > warning noise - need to look at it fresh with plenty of coffee. FWIW, Linux > generates pretty much identical code, but (of course) the BFD linker has > different behaviour from Darwin's ld64.
