|Frontend for C with gcc extensions firstname.lastname@example.org (Andrey S. Bokhanko) (2000-09-28)|
|Re: Frontend for C with gcc extensions email@example.com (Ben Pfaff) (2000-10-01)|
|Re: Frontend for C with gcc extensions firstname.lastname@example.org (John Fremlin) (2000-10-01)|
|Re: Frontend for C with gcc extensions email@example.com (2000-10-01)|
|Re: Frontend for C with gcc extensions firstname.lastname@example.org (Thomas David Rivers) (2000-10-06)|
|Re: Frontend for C with gcc extensions email@example.com (2000-10-06)|
|Re: Frontend for C with gcc extensions firstname.lastname@example.org (Dan Nicolaescu) (2000-10-06)|
|Re: Frontend for C with gcc extensions email@example.com (Andi Kleen) (2000-10-08)|
|Date:||1 Oct 2000 00:28:15 -0400|
|Organization:||AOL Bertelsmann Online GmbH & Co. KG http://www.germany.aol.com|
"Andrey S. Bokhanko" <firstname.lastname@example.org> schreibt:
>The obvious answer -- gcc frontend itself doesn't count, because it's
>not frontend in traditional sence -- it's rather an inextricable mix
>of frontend and backend.
How do you distinguish a frontend from anything else?
IMO you can strip all "backend" code off the gcc sources, in order to
obtain the desired "frontend". Of course some prodcedures must be
replaced or introduced, to create the desired output of the frontend.
As mentioned in another thread, a modern preprocessor (frontend?) can
not easily be separated from the according compiler (backend). When
e.g. your frontend should handle sizeof() expressions in conditional
statements, then it also must understand any type declarations in the
If you only want to translate gcc sources into source code for another
compiler, then you may not find such a tool in general. I often wished
only to know how to set the several BERKLEY... switches, in order to
make any other (non-Unix) compiler accept GNU source code :-(
Return to the
Search the comp.compilers archives again.