public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: binutils@sources.redhat.com, cgen@sources.redhat.com
Subject: Re: include/dis-asm.h patch for cgen disassemblers
Date: Fri, 01 Feb 2002 13:23:00 -0000	[thread overview]
Message-ID: <20020201162327.E4226@redhat.com> (raw)
In-Reply-To: <3C5B00CF.6090001@cygnus.com>; from ac131313@cygnus.com on Fri, Feb 01, 2002 at 03:55:43PM -0500

[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]

Hi -


cagney wrote:

> The PS2 has a number of ISAs on a single chip.  [...]

I hope you're not just yanking my chain.  You should realize that
the PS2 processor chip is more of a system-on-a-chip, with distinct
processors on one die.  The fact that they are on the same chip
is a fabrication decision, absurd to contemplate during bfd modelling.


> that would be #2 above.  The question is then, is this the most 
> applicable model and acceptable to BFD/BINUTILS? [...]

I don't really care -- it has no bearing on the current issue.

Maybe you are confusing the term "ISA" with the concept of a
"manual" or "book".  Maybe you are confusing an overall
architecture by a list of instructions that some implementation
of some architecture may execute in some modes.  Maybe you are
confusing my intent of using the "isas" field (to identify subsets
of the instruction sets implemented by the current arch/mach) with
some imagined plan to replace arch/mach.

Please get unconfused, for example by thinking about the
relationship between arm & thumb instructions.  Hint: a single
program can contain both.  Such an executable file can be
marked with a single bfd_arch/mach tag pair.  The processor
switches its interpretation of instruction memory contents
based upon internal run-time state.


- FChE

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2002-02-01 21:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-31  9:43 Frank Ch. Eigler
2002-01-31 12:22 ` Doug Evans
2002-01-31 13:21   ` Frank Ch. Eigler
2002-01-31 13:41     ` Doug Evans
2002-02-01 10:13       ` Frank Ch. Eigler
2002-02-01 10:22         ` Doug Evans
2002-02-01 10:28         ` Andrew Cagney
2002-02-01 10:36           ` Frank Ch. Eigler
2002-02-01 11:00             ` Andrew Cagney
2002-01-31 13:55     ` Andrew Cagney
2002-01-31 15:42       ` Frank Ch. Eigler
2002-01-31 16:03         ` Andrew Cagney
2002-01-31 16:57           ` Frank Ch. Eigler
2002-01-31 22:33             ` Andrew Cagney
     [not found]               ` <20020201092827.H6166@redhat.com>
     [not found]                 ` <3C5AE910.4090009@cygnus.com>
2002-02-01 11:56                   ` Frank Ch. Eigler
2002-02-01 12:02                     ` Andrew Cagney
2002-02-01 12:10                       ` Frank Ch. Eigler
2002-02-01 12:44                         ` Andrew Cagney
2002-02-01 12:56                           ` Andrew Cagney
2002-02-01 13:23                             ` Frank Ch. Eigler [this message]
     [not found]                               ` <3C5B1E19.8030405@cygnus.com>
2002-02-04  8:32                                 ` Frank Ch. Eigler
     [not found]                                   ` <3C601DB8.7080700@cygnus.com>
2002-02-05 11:29                                     ` Frank Ch. Eigler
2002-02-05 12:42                                       ` Doug Evans
     [not found]                     ` <3C5AF9D1.8070607@cygnus.com>
2002-02-01 12:39                       ` Frank Ch. Eigler

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=20020201162327.E4226@redhat.com \
    --to=fche@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=cagney@redhat.com \
    --cc=cgen@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).