From: YunQiang Su <yunqiang.su@cipunited.com>
To: nickc@redhat.com
Cc: binutils@sourceware.org, YunQiang Su <yunqiang.su@cipunited.com>
Subject: [PATCH v5 2/4] Gold/MIPS: Drop mips*le/mips*el* triple pattern
Date: Mon, 13 Nov 2023 13:05:47 +0800 [thread overview]
Message-ID: <20231113050549.702494-3-yunqiang.su@cipunited.com> (raw)
In-Reply-To: <20231113050549.702494-1-yunqiang.su@cipunited.com>
Only mips*el triples are supported by binutils. The mips*le
or mips*el* may cause some problem with other components of
binutils, since they will consider them as big endian.
---
gold/configure.tgt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gold/configure.tgt b/gold/configure.tgt
index 996bc901d1d..8f0f21bdc03 100644
--- a/gold/configure.tgt
+++ b/gold/configure.tgt
@@ -153,7 +153,7 @@ aarch64*-*)
targ_big_endian=false
targ_extra_big_endian=true
;;
-mips*el*-*-*|mips*le*-*-*)
+mips*el-*-*)
targ_obj=mips
targ_machine=EM_MIPS
targ_size=32
--
2.39.2
next prev parent reply other threads:[~2023-11-13 5:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 5:05 [PATCH v5 0/4] Gold/MIPS: Improve MIPS support in configure.tgt YunQiang Su
2023-11-13 5:05 ` [PATCH v5 1/4] Gold: Add targ_extra_little_endian to configure.ac YunQiang Su
2023-11-13 5:05 ` YunQiang Su [this message]
2023-11-13 5:05 ` [PATCH v5 3/4] Gold/MIPS: Add targ_extra_size=64 for mips32 triples YunQiang Su
2023-11-17 14:35 ` Nick Clifton
2023-11-17 14:57 ` YunQiang Su
2023-11-20 12:11 ` Nick Clifton
2023-11-13 5:05 ` [PATCH v5 4/4] Gold/MIPS: Add mips64*/mips64*el triple support YunQiang Su
2023-11-13 5:11 ` [PATCH v5 0/4] Gold/MIPS: Improve MIPS support in configure.tgt 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=20231113050549.702494-3-yunqiang.su@cipunited.com \
--to=yunqiang.su@cipunited.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).