Re: A89: Re: Game Programming -- Pure Assembly vs. TI-GCC?
[Prev][Next][Index][Thread]
Re: A89: Re: Game Programming -- Pure Assembly vs. TI-GCC?
Robin Kirkman wrote:
>
> A C compiler translates C code to assembly! This is done by the program 'cc1' in
> gcc.
> Next, it is assembled (by 'as' usually, but 'a68k' in ti-gcc i believe...) into
> object code.
> Then, if you have a decent linker, your object files are combined with libraries
> to make a final executable. In the case of the tigcc linker...
Here are the exact step from myfile.c to myfile.89z. The differents
programs involved are called by gcc.exe, itself called by tigcc.exe :
_first, cpp.exe (the preprocessor) take the souce file, remove every
comments in it, and execute every line starting with a # (such as
#ifdef, #include, #define etc...). You can see what is generated after
this step with the command "gcc -E myfile.c".
_next, cc1.exe (the compiler itself) convert the C code to assembly.
Note that the syntax used for assembly is not the same as used in A68k.
You can see what is generated by this step with the command : "gcc -S
myfile.c"
_next as.exe (equivalent of a68k.exe for gcc) convert the assembly code
into a binary file.
_last, link.exe (the part written by Xavier Vassor) convert the binary
file into an executable for the TI (a .89z or .9xz file).
--
Jean Canazzi
References: