public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Ben Elliston <bje@redhat.com>
To: Doug Evans <dje@transmeta.com>
Cc: cgen development <cgen@sources.redhat.com>
Subject: Re: multiple isa support
Date: Thu, 23 Nov 2000 18:12:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.30.0011241309040.2578-100000@moshpit.cygnus.com> (raw)
In-Reply-To: <14875.62361.630847.793130@casey.transmeta.com>

Hi Doug,

    > 	#include "cgen-engine.h"
    > 	#include "cpu.h"
    > 	#include "decode.h"

   I'm guessing the way to go is to have a separate #include for each
   decoder. After quick glance at m32r's decode.h and decodex.h it seems
   like they can co-exist.

I ended up leaving the code generator to emit #include "decode.h" and then
created my own decode.h which brings in the relevant decoder:

	#ifdef WANT_ISA_FOO
	#include "decode-foo.h"
	#endif

	#ifdef WANT_ISA_BAR
	#include "decode-bar.h"
	#endif

I can control this from my Makefile by passing -D options to the compiler.
I think this is probably sufficient.  I don't feel this is a problem that we
should invest a whole lot of time to solve for the sim/common framework.
We've got bigger fish to fry. :-)

Cheers, Ben

  parent reply	other threads:[~2000-11-23 18:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-20 14:33 Ben Elliston
2000-11-22  8:26 ` Doug Evans
2000-11-22 16:09   ` Ben Elliston
2000-11-22 16:29     ` Frank Ch. Eigler
2000-11-23 18:12   ` Ben Elliston [this message]
2000-12-01  6:15     ` Johan Rydberg
2000-12-01 13:43       ` Ben Elliston
  -- strict thread matches above, loose matches on Subject: below --
2000-11-19 19:52 Ben Elliston

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=Pine.LNX.4.30.0011241309040.2578-100000@moshpit.cygnus.com \
    --to=bje@redhat.com \
    --cc=cgen@sources.redhat.com \
    --cc=dje@transmeta.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).