Hello Thomas !

What do you mean by "old version of tcc" there is other newer versions
elsewhere ?

Cheers !


On Mon, Mar 31, 2014 at 3:26 PM, Thomas Preudhomme <robo...@celest.fr>wrote:

> Le 2014-03-30 21:18, Domingo Alvarez Duarte a écrit :
>
>> That would be nice !
>>
>> I would like to see the implementation of
>>
>> qcc http://lists.nongnu.org/archive/html/tinycc-devel/
>> 2011-09/txtYogaFhDvlT.txt
>> [3] and any documentation will help on it, someone asked before about
>>
>> tinycc generate an intermediate pcode that would make things easier
>> for qcc.
>>
>> When I started tinycc-noglobals it was because I was looking at a jit
>> library and found libjit very nice but its not maintained and only the
>>
>> x86 and x86_64 backends are implemented (arm is only a draft that
>> doesnt work), then I started playing with it and found the
>>
>> instructions to construct jitted code a bit complicated, knowing
>> tinycc I thought why complicate my life when I already know C and
>> tinycc generates executable code onthefly/jit ? Then I actualized my
>> virtual io on top of tinycc:mob and then started looking at the tinycc
>> code in more detail, when I found global variables like "ch, file,
>> tok" it was clear that the potential for name clashing/bugs using it
>> as is would be huge.
>>
>> Thats why tinycc-noglobals came to existence, then I found that the
>>
>> backends of tinycc was not in good shape, it can compile some simple
>> programs in general but when we try to compile something a bit more
>> complex like fossil-scm it failed.
>>
>> Then searchin the net I found the http://landley.net/qcc/ [4] ,
>> http://elinux.org/CELF_Project_Proposal/Combine_tcg_with_tcc [5] and
>>
>> looked at qemu tcg "Tiny Code Generator" and thought what a great
>> idea !!
>>
>> I propose to try make it a reality, any volunteers ???
>>
>
> Sorry I don't have much free time and I cannot work on qemu due to IP
> issues related to my work. But the idea sounds interesting. It's just a bit
> sad to use an old version of tcc as the frontend though.
>
> Thomas
>
>
> _______________________________________________
> Tinycc-devel mailing list
> Tinycc-devel@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/tinycc-devel
>
_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Reply via email to