public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: gdb-buildbot@gdb-buildbot.osci.io
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] elf32-tic6x.c: Define the default elf32_bed to elf32_tic6x_bed
Date: Wed, 8 Jul 2020 14:58:02 -0400 (EDT) [thread overview]
Message-ID: <845b83d7eba22c20acdd605e231f8b03a08ff71a@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 845b83d7eba22c20acdd605e231f8b03a08ff71a ***
commit 845b83d7eba22c20acdd605e231f8b03a08ff71a
Author: H.J. Lu <hjl.tools@gmail.com>
AuthorDate: Sun Jun 7 14:53:58 2020 -0700
Commit: H.J. Lu <hjl.tools@gmail.com>
CommitDate: Sun Jun 7 14:53:58 2020 -0700
elf32-tic6x.c: Define the default elf32_bed to elf32_tic6x_bed
Get
00000000000007c0 d elf32_tic6x_bed
0000000000000000 d elf32_tic6x_elf_bed
00000000000003e0 d elf32_tic6x_linux_bed
instead of
00000000000007c0 d elf32_bed
0000000000000000 d elf32_tic6x_elf_bed
00000000000003e0 d elf32_tic6x_linux_bed
* elf32-tic6x.c (elf32_bed): Defined the default to
elf32_tic6x_bed.
diff --git a/bfd/ChangeLog b/bfd/ChangeLog
index 0506a2971d..79a0f7aa69 100644
--- a/bfd/ChangeLog
+++ b/bfd/ChangeLog
@@ -1,3 +1,8 @@
+2020-06-07 H.J. Lu <hongjiu.lu@intel.com>
+
+ * elf32-tic6x.c (elf32_bed): Defined the default to
+ elf32_tic6x_bed.
+
2020-06-07 H.J. Lu <hongjiu.lu@intel.com>
* elf64-hppa.c (elf64_hppa_link_hash_table): Remove plt_sec and
diff --git a/bfd/elf32-tic6x.c b/bfd/elf32-tic6x.c
index d1ba4c2a93..1de4a57d5f 100644
--- a/bfd/elf32-tic6x.c
+++ b/bfd/elf32-tic6x.c
@@ -4254,6 +4254,8 @@ elf32_tic6x_write_section (bfd *output_bfd,
return TRUE;
}
+#define elf32_bed elf32_tic6x_bed
+
#define TARGET_LITTLE_SYM tic6x_elf32_le_vec
#define TARGET_LITTLE_NAME "elf32-tic6x-le"
#define TARGET_BIG_SYM tic6x_elf32_be_vec
next reply other threads:[~2020-07-08 18:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 18:58 gdb-buildbot [this message]
2020-07-08 18:58 ` Failures on Fedora-i686, branch master gdb-buildbot
2020-07-08 19:25 ` Failures on Fedora-x86_64-cc-with-index, " gdb-buildbot
2020-07-08 20:00 ` Failures on Fedora-x86_64-m64, " gdb-buildbot
2020-07-08 20:17 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2020-07-08 20:46 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2020-07-08 20:52 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2020-07-08 21:25 ` Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
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=845b83d7eba22c20acdd605e231f8b03a08ff71a@gdb-build \
--to=gdb-buildbot@gdb-buildbot.osci.io \
--cc=gdb-testers@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).