public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@transmeta.com>
To: Michael Meissner <cgen-mail@the-meissners.org>
Cc: cgen@sources.redhat.com
Subject: Re: Use of DI mode on 32-bit hosts
Date: Thu, 05 Jun 2003 16:04:00 -0000	[thread overview]
Message-ID: <16095.27119.111318.20420@xris-athlon.transmeta.com> (raw)
In-Reply-To: <20030605115059.GA16222@tiktok.the-meissners.org>

Michael Meissner writes:
 > By the way, what is the way to configure cgen?  The toplevel makefile doesn't
 > seem to go into the cgen directory, and if I configure cgen directly from the
 > subdirectory, I get the following in the tmp-desc.h file:
 > 
 > #ifndef @ARCH@_CPU_H
 > #define @ARCH@_CPU_H
 > 
 > Obviously this is a minor annoyance, but I'm wondering if I shouldn't be
 > invoking it from the toplevel Makefile.

You don't need to configure cgen to generate files.
Cgen use to get configured but that part got removed.
It's still needed to build the docs of course so that part
has to get put back.

When you configure the entire tree, add --enable-cgen-maint.
Also, add your cpu to opcodes/Makefile.am.
Grep for the other cgen cpu files in there and cut-n-paste.

Then when you go to build in opcodes, the dependencies there
will invoke cgen as appropriate.

And if you want to just generate the files and not build anything

bash$ make stamp-<cpu>

[Perhaps that's what you're doing already.
Though I'm then at a loss to explain why @ARCH@ didn't get substituted.]

      parent reply	other threads:[~2003-06-05 16:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-02 17:32 Michael Meissner
2003-06-02 17:45 ` Doug Evans
2003-06-02 19:22   ` Michael Meissner
2003-06-02 20:44     ` Doug Evans
2003-06-02 20:50       ` Frank Ch. Eigler
2003-06-02 21:26         ` Doug Evans
2003-06-02 21:32           ` Frank Ch. Eigler
2003-06-02 22:04             ` Doug Evans
2003-06-03 15:19               ` Frank Ch. Eigler
2003-06-02 21:33       ` Michael Meissner
2003-06-02 22:10         ` Doug Evans
2003-06-02 22:16           ` Doug Evans
2003-06-04 20:27         ` Doug Evans
2003-06-05 11:51           ` Michael Meissner
2003-06-05 13:34             ` Ben Elliston
2003-06-05 15:41               ` Doug Evans
2003-06-05 16:04             ` Doug Evans [this message]

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=16095.27119.111318.20420@xris-athlon.transmeta.com \
    --to=dje@transmeta.com \
    --cc=cgen-mail@the-meissners.org \
    --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).