public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@transmeta.com>
To: Jim Blandy <jimb@redhat.com>
Cc: cgen@sources.redhat.com
Subject: Re: RFA: hardware can have ISA attributes, too
Date: Mon, 06 Oct 2003 21:21:00 -0000	[thread overview]
Message-ID: <16257.56504.68603.667102@casey.transmeta.com> (raw)
In-Reply-To: <vt2pthmri0p.fsf@zenia.home>

Jim Blandy writes:
 > > I'm not sure about the patch to provide extern @arch@_cgen_hw_table though.
 > > If it's ultimately needed, great.
 > > The way it's intended to normally work is that you access the CGEN_HW_ENTRY
 > > elements via struct cgen_cpu_desc . hw_table.
 > 
 > I had considered instantiating a desc, the way the disassembler does.
 > That would work, too.  But I wasn't sure how expensive they were, and
 > I knew the information I needed was right there in the table, no
 > allocation necessary.
 > 
 > The toolchain at hand could be handling up to a dozen processor
 > variants.  There'd be a separate desc instantiated for each variant
 > the user refers to in a single GDB session.  Does that seem
 > reasonable?

Sorry for the delay!  The message got lost in my queue.

Whether it's reasonable or not I'll leave to you.
I'm guessing not but I'm not sure what the usage pattern would be.
In the end, adding the extern decl is probably a useful thing to do
anyway, so just go ahead.

  reply	other threads:[~2003-10-06 21:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-24 18:15 Jim Blandy
2003-09-27  4:11 ` Doug Evans
2003-09-27 14:13   ` Jim Blandy
2003-10-06 21:21     ` Doug Evans [this message]
2003-10-07  4:57       ` Jim Blandy

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=16257.56504.68603.667102@casey.transmeta.com \
    --to=dje@transmeta.com \
    --cc=cgen@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).