public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libffi/97166] New: libffi build issue when compiling with -mcpu=power10
Date: Tue, 22 Sep 2020 17:53:09 +0000	[thread overview]
Message-ID: <bug-97166-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97166

            Bug ID: 97166
           Summary: libffi build issue when compiling with -mcpu=power10
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libffi
          Assignee: unassigned at gcc dot gnu.org
          Reporter: bergner at gcc dot gnu.org
  Target Milestone: ---

When building libffi with -mcpu=power10, we're seeing the following linker
error.

libtool: link: gcc -shared  -fPIC -DPIC  src/.libs/prep_cif.o src/.libs/types.o
src/.libs/raw_api.o src/.libs/java_raw_api.o src/.libs/closures.o
src/powerpc/.libs/ffi.o src/powerpc/.libs/ffi_sysv.o
src/powerpc/.libs/ffi_linux64.o src/powerpc/.libs/sysv.o
src/powerpc/.libs/ppc_closure.o src/powerpc/.libs/linux64.o
src/powerpc/.libs/linux64_closure.o    -O3 -mcpu=power10 -Wl,--version-script
-Wl,libffi.map   -Wl,-soname -Wl,libffi.so.8 -o .libs/libffi.so.8.1.0
src/powerpc/.libs/linux64.o: in function `ffi_call_LINUX64':
(.text+0x40): call to `ffi_prep_args64' lacks nop, can't restore toc; (toc
save/adjust stub)
/home/bergner/gcc/install/gcc-fsf-mainline-power10/bin/ld: final link failed:
bad value
collect2: error: ld returned 1 exit status
Makefile:1028: recipe for target 'libffi.la' failed

This ends up being a bug in some POWER specific libffi asm code that doesn't
know about our new to POWER10 PCREL support.  This bugzilla is to track syncing
the fix to libffi into GCC version of libffi, which is being tracked upstream
here:

  https://github.com/libffi/libffi/pull/584

             reply	other threads:[~2020-09-22 17:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22 17:53 bergner at gcc dot gnu.org [this message]
2020-09-22 18:44 ` [Bug libffi/97166] " bergner at gcc dot gnu.org
2020-09-24  8:02 ` amodra at gmail dot com
2020-09-24 14:01 ` cvs-commit at gcc dot gnu.org
2020-09-24 14:01 ` cvs-commit at gcc dot gnu.org
2020-09-24 14:21 ` amodra at gmail dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-97166-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).