This is the mail archive of the
cgen@sources.redhat.com
mailing list for the CGEN project.
Re: binutils porting to new CPU
- From: Ralph Escherich <esche at mobilesmartsinc dot com>
- To: "Frank Ch. Eigler" <fche at redhat dot com>
- Cc: cgen at sources dot redhat dot com
- Date: Wed, 29 Oct 2003 16:31:09 -0800
- Subject: Re: binutils porting to new CPU
- References: <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