public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@transmeta.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: binutils@sources.redhat.com, cgen@sources.redhat.com
Subject: include/dis-asm.h patch for cgen disassemblers
Date: Thu, 31 Jan 2002 12:22:00 -0000	[thread overview]
Message-ID: <15449.42904.232177.265525@casey.transmeta.com> (raw)
In-Reply-To: <20020131124350.C19966@redhat.com>

Frank Ch. Eigler writes:
 > I have a scenario where I need a (cgen-based) disassembler to select
 > a given list of instruction sets of a multi-ISA processor, based on
 > a run-time condition.  This is something like the arm/thumb or
 > mips/mips16 split (odd PC), except that there is no trivial way to
 > encode the run-time condition.  The raw arch/mach parameters are
 > fixed, and there is no object file for the disassembler to look
 > into to guess from (based on PC).  So, I can either expand the
 > disassemble_info structure, or overload an existing field.  
 > 
 > I went with the latter for this patch.  It adds a new .flags option,
 > which tells cgen-based disassemblers to pull out the ISA bitmask out
 > of the .mach field.  This is no great loss, since the mach field is
 > not normally used for such purposes in cgen ports, and can be
 > overridden on a per-target basis for exceptions.
 > 
 > Any comments / objections?

Blech.
Down the road: "Oh.  This is a cgen port.  Maybe `mach' means `mach',
maybe it doesn't. :-("

methinks `mach' is too well established to overload.

I'd go with the first possibility, and not overload `mach'.
Instead of arch/mach in disassemble_info, have arch/mach/mumble
where mumble is up to each port.

[by "mumble" I mean "you pick the name", not "each port gets
to pick the name" ...]

  reply	other threads:[~2002-01-31 20:22 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 [this message]
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
     [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=15449.42904.232177.265525@casey.transmeta.com \
    --to=dje@transmeta.com \
    --cc=binutils@sources.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).