From: Andrew Cagney <ac131313@cygnus.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Andrew Cagney <cagney@redhat.com>,
binutils@sources.redhat.com, cgen@sources.redhat.com
Subject: Re: include/dis-asm.h patch for cgen disassemblers
Date: Thu, 31 Jan 2002 22:33:00 -0000 [thread overview]
Message-ID: <3C5A3694.7020502@cygnus.com> (raw)
In-Reply-To: <20020131195734.D6166@redhat.com>
> Hi -
>
> cagney wrote:
>
>> [...]
>
>> > isa ~= instruction set ~= group of machine instructions decodable;
>> > can be a function of cpu state
>
>>
>> Er, ISA == Instruction Set Architecture which to me is bfd_architecture.
>> I think, here you're looking for something else.
>>
>> For instance, Arm has thumb and MIPS has MIPS16. They are modes but
>> sill part of a single ISA.
>
>
> Yes, but not in an interesting sense. It's much like the IA32 engine
> inside IA64: they surely aren't the same ISA, despite being executable
> by the same hardware, and operating partly on the same registers.
> Sure, arm & thumb are closer together, and they may be documented in
> the same publication, but that's not substantial to this question.
Yes, and both bfd_arch_ia64 and bfd_arch_i386 are defined as separate
bfd_architectures.
> The conceptual issue is whether or not the choice of instructions
> available is a function of processor state. For the purposes of
> tools like disassemblers and simulators, and really even assemblers
> and compilers, each such group forms a separate instruction set.
Sorry, can you try that again.
Andrew
next prev parent reply other threads:[~2002-02-01 6:33 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 [this message]
[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
[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=3C5A3694.7020502@cygnus.com \
--to=ac131313@cygnus.com \
--cc=binutils@sources.redhat.com \
--cc=cagney@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=fche@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).