Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: Andrew Cagney <ac131313@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [obish] More osabi comments
Date: Mon, 27 Oct 2003 15:28:00 -0000	[thread overview]
Message-ID: <3F9D39AB.6010009@redhat.com> (raw)
In-Reply-To: <vt2llraqkls.fsf@zenia.home>


> The bfd_mach_foo things refer to ISAs, not chips.  So the
> 'can_run_code_for' is talking about whether one ISA is an
> upwards-compatible extension of another, not a question of which ISAs
> a chip may implement.  Is the ISA / chip distinction the one the
> comment is trying to make?

This is how it now reads:

       /* NOTE: cagney/2003-10-23: The code for "a can_run_code_for b"
          is implemented using BFD's compatible method (a->compatible
          (b) == a -- the lowest common denominator between a and b is
          a).  That method's definition of compatible may not be as you
          expect.  For instance the test "amd64 can run code for i386"
          (or more generally "64-bit ISA can run code for the 32-bit
          ISA").  BFD doesn't normally consider 32-bit and 64-bit
          "compatible" so it doesn't succeed.  */

enjoy,
Andrew



      reply	other threads:[~2003-10-27 15:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-24 15:43 Andrew Cagney
2003-10-24 15:57 ` Daniel Jacobowitz
2003-10-24 17:20   ` Andrew Cagney
2003-10-24 15:57 ` Kevin Buettner
2003-10-24 21:46 ` Jim Blandy
2003-10-24 22:14   ` Andrew Cagney
2003-10-24 23:31     ` Jim Blandy
2003-10-27 15:28       ` Andrew Cagney [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=3F9D39AB.6010009@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@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