On 5/5/23 4:42 PM, Jakub Jelinek wrote: > On Thu, May 04, 2023 at 02:29:34PM -0500, Peter Bergner wrote: >> Merged from upstream libffi commit: 464b4b66e3cf3b5489e730c1466ee1bf825560e0 >> >> 2023-05-03 Dan Horák <d...@danny.cz> >> >> libffi/ >> PR libffi/109447 >> * src/powerpc/ffi_linux64.c (ffi_prep_args64): Update arg.f128 pointer. > > Ok for 14/13.2/12.4 (i.e. after 12.3 is out)/11.4
Thanks, I've pushed the GCC trunk and GCC 13 commits and now that GCC 12.3 is released, I have pushed the GCC 12 backport too. I have yet to push to GCC 11 yet, due to bootstrap is broken when building GCC 11 on our Fedora 36 system, so I cannot test there yet. It also seems GCC 11 is missing some IEEE128 changes from upstream libffi that GCC 12 and later have, so it might not even be appropriate, but I'll wait for bootstrap to be restored before making any decisions. The problem seem to be that the system ld.gold which is used to link libgo.so is dying with an undefined runtime symbol: /usr/bin/ld.gold: /home/bergner/gcc/build/gcc-fsf-11-baselib-regtest/powerpc64le-linux/libstdc++-v3/src/.libs/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /usr/bin/ld.gold) collect2: error: ld returned 1 exit status Running the link command by hand or via a make in powerpc64le-linux/libgo, the link succeeds. It's only when I type make in the top level build dir where I see this error. It's almost as if the top level build machinery adds a LD_LIBRARY_PATH=... forcing the system ld.gold (which was built with a gcc12 based compiler) to pick up the build's gcc11 libstdc++ which doesn't have that symbol, rather than the gcc12 system libstdc++. Has anyone seen anything like that before? Peter
