public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amodra at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libffi/97166] libffi build issue when compiling with -mcpu=power10
Date: Thu, 24 Sep 2020 08:02:10 +0000 [thread overview]
Message-ID: <bug-97166-4-SLe3t0QhCt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97166-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97166
Alan Modra <amodra at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Assignee|unassigned at gcc dot gnu.org |amodra at gmail dot com
Last reconfirmed| |2020-09-24
CC| |amodra at gmail dot com
Status|UNCONFIRMED |ASSIGNED
--- Comment #2 from Alan Modra <amodra at gmail dot com> ---
Oops didn't put the PR number in the commit. Fixed on master with commit
08cd8d5929 and followup commit fff56af642. These two will give a working
power10 libffi even without commit 677b9150f5, the patch adding a built-in
__PCREL__ define but you'll get some linker stubs to call between pc-rel and
toc code.
next prev parent reply other threads:[~2020-09-24 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 17:53 [Bug libffi/97166] New: " bergner at gcc dot gnu.org
2020-09-22 18:44 ` [Bug libffi/97166] " bergner at gcc dot gnu.org
2020-09-24 8:02 ` amodra at gmail dot com [this message]
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-SLe3t0QhCt@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).