From: Alan Modra <amodra@gmail.com>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sourceware.org
Subject: Re: The 2.40 branch has been created
Date: Wed, 4 Jan 2023 13:35:21 +1030 [thread overview]
Message-ID: <Y7Ts8WLs3ahq2/Pv@squeak.grove.modra.org> (raw)
In-Reply-To: <87mt739186.fsf@redhat.com>
Hi Nick,
Would you like me to apply the copyright year update to the branch?
Also, the libiberty update should have merged gcc's config/picflag.m4
with ours, in order for libiberty/configure to regen without
differences on the branch. I'm going to apply the following mainline,
and will backport to the branch if that's OK?
diff --git a/config/picflag.m4 b/config/picflag.m4
index 3bd49af00e5..3f3ac744c96 100644
--- a/config/picflag.m4
+++ b/config/picflag.m4
@@ -44,6 +44,9 @@ case "${$2}" in
# sets the default TLS model and affects inlining.
$1=-fPIC
;;
+ loongarch*-*-*)
+ $1=-fpic
+ ;;
mips-sgi-irix6*)
# PIC is the default.
;;
diff --git a/libiberty/configure b/libiberty/configure
index 451af4978e7..1ccfac9fb11 100755
--- a/libiberty/configure
+++ b/libiberty/configure
@@ -5349,6 +5349,9 @@ case "${host}" in
# sets the default TLS model and affects inlining.
PICFLAG=-fPIC
;;
+ loongarch*-*-*)
+ PICFLAG=-fpic
+ ;;
mips-sgi-irix6*)
# PIC is the default.
;;
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2023-01-04 3:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-31 13:00 Nick Clifton
2023-01-02 11:41 ` Matthias Klose
2023-01-02 11:56 ` Matthias Klose
2023-01-02 12:03 ` Andreas Schwab
2023-01-02 15:59 ` Christophe Lyon
2023-01-02 23:05 ` Mark Wielaard
2023-01-03 17:29 ` Christophe Lyon
2023-01-04 0:35 ` Mark Wielaard
2023-01-04 10:31 ` Christophe Lyon
2023-01-04 11:07 ` Mark Wielaard
2023-01-09 16:00 ` Christophe Lyon
2023-01-04 12:16 ` Nick Alcock
2023-01-10 12:43 ` Nick Alcock
2023-01-04 3:05 ` Alan Modra [this message]
2023-01-04 9:36 ` Nick Clifton
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=Y7Ts8WLs3ahq2/Pv@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
/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).