From: Steve Ellcey <sellcey@caviumnetworks.com>
To: <binutils@sourceware.org>, gdb-patches <gdb-patches@sourceware.org>
Subject: [PATCH] Patch 1 of 2 for aarch64 ILP32 support in gdb
Date: Wed, 25 Jan 2017 00:19:00 -0000 [thread overview]
Message-ID: <1485303529.29977.8.camel@caviumnetworks.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]
This is a follow up to a post from some time ago to enable aarch64
ILP32 support in gdb.
https://sourceware.org/ml/binutils/2016-09/msg00004.html
Andrew Pinksi submitted these patches and I have updated them,
addressed the comments that were made at the time, and retested
them.  Andrew broke them down into 3 patches I am submitting it as two
patches, this first one is the changes to bfd.  This patch removes the
ilp32/lp64 checking that is done in compatible and moves it to
elfNN_aarch64_merge_private_bfd_data.  Doing it in compatible is too
early for gdb.  The patch also adds an endianness check to
elfNN_aarch64_merge_private_bfd_data.  The second patch will contain
the gdb changes.
Steve Ellcey
sellcey@cavium.com
2017-01-24  Andrew Pinski  <apinski@cavium.com>
    Steve Ellcey  <sellcey@cavium.com>
* cpu-aarch64.c (compatible):
Don't reject different ILP32/LP64 ABI's here.
* elfnn-aarch64.c (elfNN_aarch64_merge_private_bfd_data):
Add an error message on why endianess is rejected.
Reject different ILP32/LP64 ABI settings.
[-- Attachment #2: bfd.patch --]
[-- Type: text/x-patch, Size: 2161 bytes --]
diff --git a/bfd/cpu-aarch64.c b/bfd/cpu-aarch64.c
index 7cb81f3..63fba48 100644
--- a/bfd/cpu-aarch64.c
+++ b/bfd/cpu-aarch64.c
@@ -25,7 +25,8 @@
/* This routine is provided two arch_infos and works out which Aarch64
machine which would be compatible with both and returns a pointer
- to its info structure. */
+ to its info structure. ABI (ilp32 vs. lp64) and endianness compatibility
+ are checked in elfNN_aarch64_merge_private_bfd_data. */
static const bfd_arch_info_type *
compatible (const bfd_arch_info_type * a, const bfd_arch_info_type * b)
@@ -38,10 +39,6 @@ compatible (const bfd_arch_info_type * a, const bfd_arch_info_type * b)
if (a->mach == b->mach)
return a;
- /* Don't allow mixing ilp32 with lp64. */
- if ((a->mach & bfd_mach_aarch64_ilp32) != (b->mach & bfd_mach_aarch64_ilp32))
- return NULL;
-
/* Otherwise if either a or b is the 'default' machine
then it can be polymorphed into the other. */
if (a->the_default)
diff --git a/bfd/elfnn-aarch64.c b/bfd/elfnn-aarch64.c
index c86a3e1..9b82f4b 100644
--- a/bfd/elfnn-aarch64.c
+++ b/bfd/elfnn-aarch64.c
@@ -6597,11 +6597,26 @@ elfNN_aarch64_merge_private_bfd_data (bfd *ibfd, struct bfd_link_info *info)
/* Check if we have the same endianess. */
if (!_bfd_generic_verify_endian_match (ibfd, info))
- return FALSE;
+ {
+ (*_bfd_error_handler)
+ (_("%B: endianness incompatible with that of the selected emulation"),
+ ibfd);
+ return FALSE;
+ }
if (!is_aarch64_elf (ibfd) || !is_aarch64_elf (obfd))
return TRUE;
+ /* Don't allow mixing ilp32 with lp64. */
+ if ((bfd_get_arch_info (ibfd)->mach & bfd_mach_aarch64_ilp32)
+ != (bfd_get_arch_info (obfd)->mach & bfd_mach_aarch64_ilp32))
+ {
+ (*_bfd_error_handler)
+ (_("%B: ABI is incompatible with that of the selected emulation: \"%s\" != \"%s\""),
+ ibfd, bfd_get_target (ibfd), bfd_get_target (obfd));
+ return FALSE;
+ }
+
/* The input BFD must have had its flags initialised. */
/* The following seems bogus to me -- The flags are initialized in
the assembler but I don't think an elf_flags_init field is
next reply other threads:[~2017-01-25 0:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 0:19 Steve Ellcey [this message]
2017-01-25 10:45 ` Nick Clifton
2017-01-25 15:37 ` Yao Qi
2017-01-25 19:44 ` Steve Ellcey
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=1485303529.29977.8.camel@caviumnetworks.com \
--to=sellcey@caviumnetworks.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@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