Re: [Tinycc-devel] Do you know of any forks of TinyCC?

[David Mertens]

Nope. I had to learn by diving into the source myself. But if you want to learn the process of compilation, you should just try to follow the series of function calls to compile code. You could, for example, load tcc in gdb and set a breakpoint on one of the parsing functions, then look at the stack trace. This is how I really started to get my head wrapped around tcc's parsing, at least.

David

On Fri, May 6, 2016 at 1:16 AM, <address@hidden> wrote:

I want to understand how TCC works, in the way it is now it confuses me greatly. Maybe you know of some forks that maybe dropped some of it's features and made source a bit easier to understand? Or, maybe I should look at some old enough commit, before TCC learned to compile asm code, and things of this sort?

_______________________________________________
Tinycc-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

--

 "Debugging is twice as hard as writing the code in the first place.
  Therefore, if you write the code as cleverly as possible, you are,
  by definition, not smart enough to debug it." -- Brian Kernighan