On Fri, Dec 4, 2009 at 2:51 PM, grischka <[email protected]> wrote:

> k1w1 wrote:
>
>> I would like to be able to maintain multiple sets of debug information in
>> RAM for multiple separate programs, so it seems like I need to move the
>> stabs sections into the TCCState structure to support this.
>>
>
> You just cannot atm. do compilation in more than one state at the
> same time.  But after you finished compilation, you can create
> another state and do another compilation, and you can keep as many
> states around as you like, including the runnable code and debug info.
>
>
>  My main objective is not to have any #includes for .c files, and to have a
>> .h file corresponding to each .c file. One implication of this will be that
>> the makefile will need to be a bit more complex because the conditional
>> including of code (like the -asm.c file to use) will need to be determined
>> at build time.
>>
>
> That is only one problem.
>
> The other is to extract all the prototypes into the .h files, and
> to adjust them for static vs. non-static.
>

This is exactly what I am doing. It is pretty tedious, but I think that once
it is done it will be easier to navigate the code. As I extract the
prototypes into the header files it is clear how the names of many functions
and variables could be improved to make it clearer what they do and which
part of the code they relate to ... but that is a project for another day.

Regards, K1w1.
_______________________________________________
Tinycc-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/tinycc-devel

Reply via email to