|Need a C compiler for a new processor. firstname.lastname@example.org (Guillaume Comeau) (1999-10-16)|
|Re: Need a C compiler for a new processor. email@example.com (Tim Josling) (1999-10-17)|
|Re: Need a C compiler for a new processor. firstname.lastname@example.org (Laurent Guerby) (1999-10-18)|
|Re: Need a C compiler for a new processor. email@example.com (Michael Meissner) (1999-10-18)|
|Re: Need a C compiler for a new processor. C.vanReeuwijk@twi.tudelft.nl (Kees van Reeuwijk) (1999-10-18)|
|Re: Need a C compiler for a new processor. firstname.lastname@example.org (Preston Gurd) (1999-10-21)|
|Re: Need a C compiler for a new processor. email@example.com (Haibing Ma) (1999-10-27)|
|Re: Need a C compiler for a new processor. firstname.lastname@example.org (Thilo Gaul) (1999-11-09)|
|Re: Need a C compiler for a new processor. email@example.com (Shirley L Coffie) (1999-11-16)|
|Re: Need a C compiler for a new processor. firstname.lastname@example.org (Mark Grosberg) (1999-11-18)|
|From:||Michael Meissner <email@example.com>|
|Date:||18 Oct 1999 00:26:54 -0400|
"Guillaume Comeau" <firstname.lastname@example.org> writes:
> 1. I am in charge of writing a C compiler for a new 32-bit
> processor. The processor itself is new, it uses an instruction set
> different than any other processor.
It depends on how different the processor is from other processors.
The more different it is from existing targets, the harder the work
will probably be (this should be true of any retargetable compiler).
> 2. I must support C, and there is no need for any library or
> extension. All it must do is compile straight ANSI-C code.
I find in the embedded world that C only targets, tend to come back in
N months asking for C++ or more recently Java. Of course if you have
a captive audience that is just working on one program and you will
never ever have the chip be used for anything else that is probably a
> 3. I am looking for the shortest path solution. I was told a compiler
> was a two man-year job, which is too long for my taste. I'd rather use
> an existing C front-end and map the result into my instruction set if
> at all possible.
Doing a GCC port should be considerably less time than 2 calendar
years. Obviously, there is a long start up time if you aren't already
a core GCC engineer. Assuming the processor has no surprises and you
are working on it full time, I would imagine a 3-6 month time frame
should be adequate to be producing initial code, if you are coming
into it cold. Add 1-2 months if you need to port an assembler and
linker as well (this can be done by another person). Of course there
is a lot of refinement in the machine description that can take months
and years afterwards.
> 4. There are lots of sites and posts pointing to GNU, which could be a
> good start. However, it supports C++ which will complicate my work. I
> also didn't find the processor-specific files (but I still have some
> more digging to do).
The machine/os specific files are in:
> [It's probably easier to retarget lcc. It's a smaller compiler, and it
> has a nice book to document it. See the FAQ. -John]
Michael Meissner, Cygnus Solutions
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886
email: email@example.com phone: 978-486-9304 fax: 978-692-4482
Return to the
Search the comp.compilers archives again.