From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: binutils@sourceware.org
Subject: [PATCH] gas: Change ELF flags initial value in rx-linux
Date: Wed, 29 Apr 2020 21:47:24 +0900 [thread overview]
Message-ID: <20200429124724.1894-2-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <20200429124724.1894-1-ysato@users.sourceforge.jp>
rx-linux uses the common GCC ABI.
Setting RX ABI in ELF flags is wrong.
For rx-linux, change to generate GCC ABI objects.
gas/ChangeLog
2020-04-27 Yoshinori Sato <ysato@users.sourceforge.jp>
* config/tc-rx.c (elf_flags): Reset default value.
(md_parse_option): For rx-elf Initialize elf_flags with RX_ABI.
---
gas/config/tc-rx.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/gas/config/tc-rx.c b/gas/config/tc-rx.c
index febdb5ab95..e3521d3193 100644
--- a/gas/config/tc-rx.c
+++ b/gas/config/tc-rx.c
@@ -42,12 +42,13 @@ const char EXP_CHARS[] = "eE";
const char FLT_CHARS[] = "dD";
\f
/* ELF flags to set in the output file header. */
-static int elf_flags = E_FLAG_RX_ABI;
+static int elf_flags;
#ifndef TE_LINUX
bfd_boolean rx_use_conventional_section_names = FALSE;
#else
bfd_boolean rx_use_conventional_section_names = TRUE;
+static int elf_flags;
#endif
static bfd_boolean rx_use_small_data_limit = FALSE;
@@ -129,6 +130,9 @@ struct cpu_type cpu_type_list[] =
int
md_parse_option (int c ATTRIBUTE_UNUSED, const char * arg ATTRIBUTE_UNUSED)
{
+#ifndef TE_LINUX
+ elf_flags = E_FLAG_RX_ABI;
+#endif
switch (c)
{
case OPTION_BIG:
--
2.20.1
next prev parent reply other threads:[~2020-04-29 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 12:47 [PATCH] ld: Add rx-linux emulation Yoshinori Sato
2020-04-29 12:47 ` Yoshinori Sato [this message]
2020-04-30 12:37 ` [PATCH] gas: Change ELF flags initial value in rx-linux Nick Clifton
2020-04-30 12:37 ` [PATCH] ld: Add rx-linux emulation 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=20200429124724.1894-2-ysato@users.sourceforge.jp \
--to=ysato@users.sourceforge.jp \
--cc=binutils@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).