From: Dave Brolley <brolley@redhat.com>
To: Steve Woloschek <steve@zbuda.com>
Cc: cgen@sourceware.org
Subject: Re: opc-file-path
Date: Mon, 15 Sep 2008 15:53:00 -0000 [thread overview]
Message-ID: <48CE84CB.7000604@redhat.com> (raw)
In-Reply-To: <1221485321.7469.34.camel@gateway.zbuda.com>
Steve Woloschek wrote:
> I am working on a port of a new processor core and have run into an
> issue when running desc-cpu.c[c|h].
>
> ./desc-cpu.scm:1038:32: In expression (opc-file-path):
> ./desc-cpu.scm:1038:32: Unbound variable: opc-file-path
>
> It appears the scripts assume there is an '[cpu].opc' file. I noticed
> that several processors in the /cpu directory do not have a .opc file.
>
The only one I ses is the cris.cpu file. The others are all part of
archirectures that do have a .opc file. Not sure why cris doesn't have
one. I've never tried to build it.
> Any thoughts on how to get around this feature?
>
I would suggest creating a minimal .opc file. $src/cgen/cpu/i960.opc
seems to be a minimal example you can clone. You can probably get rid of
the CGEN_PRINT_INSN macro and keep the rest. At some point you will
probably want to optimize the CGEN_DIS_HASH* macros for you particular port.
I hope this helps,
Dave
next prev parent reply other threads:[~2008-09-15 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 13:28 opc-file-path Steve Woloschek
2008-09-15 15:53 ` Dave Brolley [this message]
2008-09-15 22:26 ` opc-file-path Steve Woloschek
2008-09-17 16:30 ` opc-file-path Dave Brolley
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=48CE84CB.7000604@redhat.com \
--to=brolley@redhat.com \
--cc=cgen@sourceware.org \
--cc=steve@zbuda.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).