C parsing + register allocation

[Philip Herron]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey

This a design question about the c front-end of 'a' compiler. I am
working on a basic compiler atm. But i was wondering, should you have
2 parsers, it seems it may be a good idea to have a seperate parser to
run first, to do all c-preprocessor work, then have the 2nd to do the
actual code parsing into internal representation, then output assembly...

I am looking through old gcc to get to grips with how its working at
the moment, but i was also wondering for the compilation process, does
gcc output asm then call gas from something like 'execl' or does it do
this internaly at the moment? Its something i don't really see. It
seems in old gcc it was called as there was direct paths hard-coded to
the bin-utils binaries like ld,as in gcc. To call to compile. Or is it
better to directly have some interface to an assembler. Passing a
gimple like representation to it or somthing.

My knowledge is bad when it comes to interfacing with bin-utils, there
isn't much documentation on them.

Also i was wondering is there any good documenation on how gcc or in
general on linux or otherwise the register allocation process.

- -Phil
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAknzQZAACgkQAhcOgIaQQ2GsyQCcCFmqMxYgcmsTTzD37ev8c7EC
5vMAnira8dOVBi1UyXnWJONYzYO4sjUD
=IUvp
-----END PGP SIGNATURE-----