On Sun, Oct 24, 2021 at 1:36 PM Iain Sandoe <idsan...@googlemail.com> wrote: > > Hi H.J. > > > On 19 Oct 2021, at 19:01, H.J. Lu via Gcc-patches <gcc-patches@gcc.gnu.org> > > wrote: > > > > On Tue, Oct 19, 2021 at 8:03 AM David Edelsohn <dje....@gmail.com> wrote: > >> > > >> My colleague built GCC, including GCC Go, with your patch: > >> > >> "I was able to build libgo and test it partially. The results are > >> similar to the current master without libffi updates. But 64bit tests > >> aren't working in both cases. It's related to LIBPATH issues..." > >> > > > > Thanks for checking. I will rebase and retest. If there is no regression, > > I will check them in. > > At r12-4638. > > It seems that there are quite a few m32 libffi fails on x86_64-linux-gnu > [gcc123]. > > It seems that all-languages bootstrap is broken on BE powerpc64-linux-gnu > [gcc110]: > > ../../../src-patched/libffi/src/powerpc/linux64_closure.S:404: Error: > unrecognized opcode: `lvx' > make[4]: *** [src/powerpc/linux64_closure.lo] Error 1 > > could you take a look please?
Does it fail in libffi upstream? If yes, please open an issue in libffi upstream. If not, why does it fail in GCC? -- H.J.
