> Mike writes:
Mike> Is there a short list of steps to get a very minimal machine specific
Mike> back end going? Please point me to some better documents? :)
http://gcc.gnu.org/wiki/GettingStarted
http://www.cfdvs.iitb.ac.in/~amv/gcc-int-docs/
Most new backends start by copying an exist
http://gcc.gnu.org/onlinedocs/gccint/Back-End.html
This mentions a file "config.gcc" which I can't find in the GCC source.
This page tells too little I guess.
Its under the 'gcc' directory.
Aaron
http://gcc.gnu.org/onlinedocs/gccint/Back-End.html
This mentions a file "config.gcc" which I can't find in the GCC source.
This page tells too little I guess.
http://gcc.gnu.org/onlinedocs/gccint/Machine-Desc.html
This stuff would be useful if the GCC build process recognized that I
made s
"Domagoj D" <[EMAIL PROTECTED]> writes:
> Does GCC front- and middle-end keep the source code line numbers all
> the way until the RTL is generated? I'd need that for the tool I'm
> developing.
Yes. They have to, in order to generate correct debugging
information.
> Also, are there any simple s
Hi,
Does GCC front- and middle-end keep the source code line numbers all the way
until the RTL is generated? I'd need that for the tool I'm developing.
Also, are there any simple source code browsers / static analysis tools that
use GCC as the front-/middle-end that I might check out to see ho
