public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: cgen@sources.redhat.com
Subject: RFA: hardware can have ISA attributes, too
Date: Wed, 24 Sep 2003 18:15:00 -0000	[thread overview]
Message-ID: <vt24qz2oz1a.fsf@zenia.home> (raw)


I don't really feel like I understand CGEN's data model well enough to
know whether this is really appropriate, or just a kludge.

Here's the motivation.  We have a toolchain that supports several
different machines within a family; some register sets are present on
some machines, but not on others.  Given an ISA, we want to be able to
traverse the hardware list and see which register sets are available
on that ISA.

So along with this will come another patch that produces an extern
declaration for @arch@_cgen_hw_table, so we can traverse it.

What's the best way to do this?

2003-07-22  Jim Blandy  <jimb@redhat.com>

	* mach.scm (def-isa-attr!): hardware can have ISA attributes, too.

Index: cgen/mach.scm
===================================================================
RCS file: /cvs/cvsfiles/devo/cgen/mach.scm,v
retrieving revision 1.47.34.1
diff -c -r1.47.34.1 mach.scm
*** cgen/mach.scm	5 Jun 2002 22:18:35 -0000	1.47.34.1
--- cgen/mach.scm	22 Jul 2003 16:47:16 -0000
***************
*** 501,507 ****
        ; for it.
        (if (= (length isas) 1)
  	  '(for)
! 	  '(for ifield operand insn))
        (cons 'values isa-enums))
      )
  
--- 501,507 ----
        ; for it.
        (if (= (length isas) 1)
  	  '(for)
! 	  '(for ifield operand insn hardware))
        (cons 'values isa-enums))
      )
  

             reply	other threads:[~2003-09-24 18:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-24 18:15 Jim Blandy [this message]
2003-09-27  4:11 ` Doug Evans
2003-09-27 14:13   ` Jim Blandy
2003-10-06 21:21     ` Doug Evans
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=vt24qz2oz1a.fsf@zenia.home \
    --to=jimb@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).