From: Ralph Escherich <esche@mobilesmartsinc.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: cgen@sources.redhat.com
Subject: Re: binutils porting to new CPU
Date: Thu, 30 Oct 2003 00:29:00 -0000 [thread overview]
Message-ID: <200310291631.09486.esche@mobilesmartsinc.com> (raw)
In-Reply-To: <20031029165027.GA30779@redhat.com>
I tried building binutils-2.14 for the openrisc-elf target and get the
following error message:
openrisc-asm.c: In function `openrisc_cgen_assemble_insn':
openrisc-asm.c:584: error: `CGEN_INSN_RELAX' undeclared (first use in this
function)
openrisc-asm.c:584: error: (Each undeclared identifier is reported only once
openrisc-asm.c:584: error: for each function it appears in.)
make[3]: *** [openrisc-asm.lo] Error 1
openrisc-asm.c was generated by cgen
Any ideas??
Esche
On Wednesday 29 October 2003 08:50, Frank Ch. Eigler wrote:
> Hi -
>
> > [...]
> > Do you have a more detailed API description of what is generated and
> > how it should be used for porting the binutils? [...]
>
> There isn't a really good list, I'm afraid. None of those who have
> built a complete port took the extra time to document all the steps
> and nuances. It's all rather vernacular: start based on an existing
> port, do a massive search & replace for a new port name, ask here when
> you run into trouble. A simple port may go smoothly enough not to
> need any help.
>
> > Also gas/cgen.c contains code for fixups and parsing. How does all
> > this fit into the big picture of porting binutils to a new cpu target?
>
> It's a necessary detail. The fewer addressing modes your target
> supports,
> and the simpler the layout of the operands that parametrize any given
> address, the simpler (to almost nonexistent) these functions can be.
>
> > How do fixups and frags ??? fit into the API? [...]
>
> They barely do. Some CGEN operand parsing functions plop fixups into
> the assembler, for ultimate disposition as an assembly-time constant,
> or emission as a link-time relocation. Frags are little
> partially-filled-in byte strings that are concatenated ultimately
> to form object code. All this is deep GAS/BFD magic, not really cgen
> related.
>
>
> - FChE
--
Ralph Escherich 2900 Gordon Avenue Suite 203
Senior IC Design Engineer Santa Clara, CA 95051-0718
Phone: 408-328-9333
Fax: 408-735-1163
http://www.mobilesmartsinc.com
next prev parent reply other threads:[~2003-10-30 0:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 2:20 Ralph Escherich
2003-10-29 2:48 ` Frank Ch. Eigler
2003-10-29 16:37 ` Ralph Escherich
2003-10-29 16:50 ` Frank Ch. Eigler
2003-10-30 0:29 ` Ralph Escherich [this message]
2003-10-30 1:53 ` Ben Elliston
2003-10-30 5:46 ` Ralph Escherich
2003-10-30 6:43 ` Ben Elliston
2003-10-30 16:47 ` Ralph Escherich
2003-10-31 4:25 ` 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=200310291631.09486.esche@mobilesmartsinc.com \
--to=esche@mobilesmartsinc.com \
--cc=cgen@sources.redhat.com \
--cc=fche@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).