From: Ben Elliston <bje@redhat.com>
To: Jose Luis Ayala <jayala@die.upm.es>
Cc: cgen@sources.redhat.com
Subject: Re: Calling C functions
Date: Tue, 12 Mar 2002 02:02:00 -0000 [thread overview]
Message-ID: <15501.53649.353207.665381@scooby.brisbane.redhat.com> (raw)
In-Reply-To: <1015926799.4568.6.camel@eureka>
Hi.
>>>>> "Jose" == Jose Luis Ayala <jayala@die.upm.es> writes:
Jose> I'm working with the arm7.cpu architecture and I've addded calls to C
Jose> functions with c-raw-call sentences. These functions have been written
Jose> into an arm7.opc file. However, recompilation of the opcodes directory
Jose> does not read this file and does not generate the resulting
Jose> files.
It would probably be best to post some fragments of your .opc file, if
you can, but from memory, the .opc file must follow the name of the
arch (as defined in the cpu description), not the filename of the .cpu
file. This is, admittedly, a bit of a gotcha.
Try renaming arm7.opc to arm.opc and regenerate--see if that helps.
Ben
next prev parent reply other threads:[~2002-03-12 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 1:53 Jose Luis Ayala
2002-03-12 2:01 ` Frank Ch. Eigler
2002-03-12 2:02 ` Ben Elliston [this message]
2002-03-12 17:58 ` Johan Rydberg
2002-03-12 18:41 ` 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=15501.53649.353207.665381@scooby.brisbane.redhat.com \
--to=bje@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=jayala@die.upm.es \
/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).