From: Nick Clifton <nickc@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] Gold/MIPS: Add targ_extra_size=64 for mips32 triples
Date: Fri, 17 Nov 2023 14:34:07 +0000 (GMT) [thread overview]
Message-ID: <20231117143407.EA4FF3858437@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=619a8a364d6cdc43d6677f86369aa2b5d1a1cc0f
commit 619a8a364d6cdc43d6677f86369aa2b5d1a1cc0f
Author: YunQiang Su <yunqiang.su@cipunited.com>
Date: Fri Nov 17 14:33:33 2023 +0000
Gold/MIPS: Add targ_extra_size=64 for mips32 triples
Diff:
---
gold/ChangeLog | 8 ++++++--
gold/configure.tgt | 2 ++
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/gold/ChangeLog b/gold/ChangeLog
index 52379168fac..872ba7efdbb 100644
--- a/gold/ChangeLog
+++ b/gold/ChangeLog
@@ -1,3 +1,7 @@
+2023-11-17 YunQiang Su <yunqiang.su@cipunited.com>
+
+ * configure.tgt (mips targets): Set targ_extra_size=64.
+
2023-11-15 Arsen Arsenović <arsen@aarsen.me>
* aclocal.m4: Regenerate.
@@ -7,8 +11,8 @@
2023-11-10 YunQiang Su <yunqiang.su@cipunited.com>
- * configure.tgt (targ_machine): Set to EM_MIPS for little endian
- mips targets.
+ * configure.tgt (mips targets): Set targ_machine to EM_MIPS for
+ little endian mips targets.
2023-09-05 Roland McGrath <mcgrathr@google.com>
diff --git a/gold/configure.tgt b/gold/configure.tgt
index 751c8fd06c6..836727f67de 100644
--- a/gold/configure.tgt
+++ b/gold/configure.tgt
@@ -157,6 +157,7 @@ mips*el*-*-*|mips*le*-*-*)
targ_obj=mips
targ_machine=EM_MIPS
targ_size=32
+ targ_extra_size=64
targ_big_endian=false
targ_extra_big_endian=true
;;
@@ -164,6 +165,7 @@ mips*-*-*)
targ_obj=mips
targ_machine=EM_MIPS
targ_size=32
+ targ_extra_size=64
targ_big_endian=true
targ_extra_big_endian=false
;;
next reply other threads:[~2023-11-17 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 14:34 Nick Clifton [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-28 3:44 YunQiang Su
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=20231117143407.EA4FF3858437@sourceware.org \
--to=nickc@sourceware.org \
--cc=bfd-cvs@sourceware.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).