public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tristan Gingold <gingold@adacore.com>
To: Marcus Shawcroft <marcus.shawcroft@gmail.com>
Cc: Richard Earnshaw <rearnsha@arm.com>,
	"binutils@sourceware.org Development" <binutils@sourceware.org>
Subject: Re: [Mach-O, committed]: Add definition for arm64 cpu
Date: Thu, 27 Mar 2014 08:22:00 -0000	[thread overview]
Message-ID: <397AF0F1-ED4E-4805-B79E-3862D2A4FF7E@adacore.com> (raw)
In-Reply-To: <CAFqB+PyAoAyFwwU9qj5uGKfSHLUA-peH+XFX=599ff4nDRYePQ@mail.gmail.com>


On 26 Mar 2014, at 17:43, Marcus Shawcroft <marcus.shawcroft@gmail.com> wrote:

> On 26 March 2014 16:34, Tristan Gingold <gingold@adacore.com> wrote:
> 
>> In fact it is consistent with the macro name defined by Apple :-(
>> Hard to be consistent with two non-consistent usages.
> 
> That justification does not hold for the name string in bfd_mach_o_cpu_name[].

The strings in bfd_mach_o_cpu_name corresponds to the cpu name part in the literal.
This is also compatible with the output of Apple tool:

/SDKs/iPhoneOS7.1.sdk/Developer/Library/Frameworks/SenTestingKit.framework/SenTestingKit (architecture arm64):

Note that (obviously) the BFD architecture of such binaries is bfd_arch_aarch64, and so will be
the bfd target.

Tristan.

      parent reply	other threads:[~2014-03-27  8:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26 15:10 Tristan Gingold
2014-03-26 16:24 ` Richard Earnshaw
2014-03-26 16:34   ` Tristan Gingold
2014-03-26 16:43     ` Marcus Shawcroft
2014-03-26 16:49       ` Richard Earnshaw
2014-03-27  8:18         ` Tristan Gingold
2014-03-27  8:22       ` Tristan Gingold [this message]

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=397AF0F1-ED4E-4805-B79E-3862D2A4FF7E@adacore.com \
    --to=gingold@adacore.com \
    --cc=binutils@sourceware.org \
    --cc=marcus.shawcroft@gmail.com \
    --cc=rearnsha@arm.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).