From: Andrew Cagney <ac131313@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
Andrew Cagney <cagney@redhat.com>,
binutils@sources.redhat.com, cgen@sources.redhat.com
Subject: Re: include/dis-asm.h patch for cgen disassemblers
Date: Fri, 01 Feb 2002 12:56:00 -0000 [thread overview]
Message-ID: <3C5B00CF.6090001@cygnus.com> (raw)
In-Reply-To: <3C5AFE3C.6050405@cygnus.com>
> I chose the PS2 because its architecture is public and, I think, it very much illustrates the underlying issue of the current discussion.
>
> The PS2 has a number of ISAs on a single chip. What is the correct way to define this from bfd? If you don't feel comfortable with answering this, then hopefully someone else will. Off the top of my head I can think of several ways:
>
> bfd_arch_mips
> bfd_mach_mips_ps2mips
> bfd_mach_mips_ps2video
>
> bfd_arch_ps2
> bfd_mach_ps2mips
> bfd_mach_ps2video
>
> bfd_arch_mips
> bfd_mach_mips_ps2
> bfd_arch_ps2video
>
> I think BFD to clearly document how this should be done, your isas is very much part of this.
Sorry, you did answer this.
>> We did whatever must have seemed most useful at the time for their
>> treatment ... one bfd_arch, a bunch of bfd_mach's. Note that all
>> those coprocessors have a static set of instructions.
that would be #2 above. The question is then, is this the most
applicable model and acceptable to BFD/BINUTILS?
It definitly means a sideways twist since ps2mips is a member of the
bfd_arch_mips family.
Andrew
next prev parent reply other threads:[~2002-02-01 20:56 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 [this message]
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=3C5B00CF.6090001@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).