From: Shehryar Humayun <shehryarhumayunkhan@yahoo.com>
To: Ben Elliston <bje@redhat.com>
Cc: cgen@sources.redhat.com
Subject: Re: Next Step
Date: Tue, 03 Sep 2002 20:51:00 -0000 [thread overview]
Message-ID: <20020904035132.81503.qmail@web21201.mail.yahoo.com> (raw)
In-Reply-To: <15732.50638.496629.614616@tooth.toronto.redhat.com>
Hi,
Thanks for the response. It worked out quite well. I
have been able to generate 8 opcodes support files for
m32r as well as fr30. Just one thing, When I invoke
the make process, in the end it prints:
Generating m32r-opc.h
Generating m32r-opc.c
...
When the make process terminates, the files generated
are named tmp-opc.c, tmp-opc.h, tmp-*.*, rather than
m32r-*.c. Is this okay? Moreover, the files do not
contain the name of the architecture e.g. m32r, rather
<arch> is written every where in the file. Is this thw
way it is supposed to be?
Regards
--- Ben Elliston <bje@redhat.com> wrote:
> Hi.
>
> >>>>> "Shehryar" == Shehryar Humayun
> <shehryarhumayunkhan@yahoo.com> writes:
>
> Shehryar> At the end of step 3, I get a message
> "Done analysis"
> Shehryar> and I get the prompt "guile>".
> Shehryar> Porting guide for CGEN says that next
> step is to
> Shehryar> "run generators until output looks
> reasonable, e.g.
> Shehryar> (cgen-opc.c)"
>
> Shehryar> - What is meant by "generator". Is it
> .scm files in
> Shehryar> cgen source directory we are talking
> about?
>
> Yes.
>
> Shehryar> - How exactly do I implement this phrase
> "until output
> Shehryar> looks reasonable" in the statement? What
> should I
> Shehryar> write at guile prompt? What is the
> criteria for
> Shehryar> reasonable output?
>
> You should not bother running cgen in this tedious
> way. If you are
> doing an opcodes port, use the infrastructure in
> place in the
> src/opcodes/Makefile.{am,in} to run CGEN for you. I
> think this point
> has been discussed before.
>
> Shehryar> - Where are the output files located
> e.g.
> Shehryar> cgen-opc.[ch], cgen-desc.[ch]?
>
> I believe there is an application-switch to specify
> where the
> generated files should go. Again, this is handled
> for you by the
> opcodes Makefile.
>
> Shehryar> Hoping for an early response, beed it
> badly!
>
> Sorry it took so long -- it was a three-day weekend.
>
> Ben
__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com
next prev parent reply other threads:[~2002-09-04 3:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-01 2:03 Shehryar Humayun
2002-09-03 7:23 ` Ben Elliston
2002-09-03 20:51 ` Shehryar Humayun [this message]
2002-09-04 11:11 ` Ben Elliston
2002-09-04 19:42 ` Shehryar Humayun
2002-09-05 2:30 ` Ben Elliston
2002-09-05 16:22 ` Shehryar Humayun
2002-09-06 6:55 ` Ben Elliston
2002-09-06 7:37 ` Problem in opcodes for ARM Shehryar Humayun
2002-09-06 9:02 ` Doug Evans
2002-09-06 11:37 ` Shehryar Humayun
2002-09-06 9:36 ` Next Step Shehryar Humayun
2002-09-06 10:03 ` Ben Elliston
2002-09-06 11:21 ` Shehryar Humayun
2002-09-06 12:07 ` Ben Elliston
2002-09-06 20:54 ` Shehryar Humayun
2002-09-09 6:27 ` Ben Elliston
2002-09-03 20:51 ` Shehryar Humayun
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=20020904035132.81503.qmail@web21201.mail.yahoo.com \
--to=shehryarhumayunkhan@yahoo.com \
--cc=bje@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).