[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tinycc-devel] make tcc reentrant

From: Ulrich Schmidt
Subject: Re: [Tinycc-devel] make tcc reentrant
Date: Tue, 3 Dec 2019 09:33:17 +0100
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2


I dod not change the api. Only the internal storage of internal static
vars need to be moved to the compilation state struct.


Am 03.12.2019 um 09:30 schrieb Christian Jullien:

Even if I don't currently need it, with multi-core, multi-thread modern CPU, it 
is always a good principle to make reentrant any software components.
I personally vote for it but, as it is a major change, especially regarding the 
API, I prefer if it starts after 0.9.27. BTW, 0.9.27 is about 2 years old. It's 
probably time to freeze it and start 0.9.28 with possibly reentrant feature as 
main goal.

Maintainers, wdyt?


-----Original Message-----
From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=address@hidden] On 
Behalf Of Ulrich Schmidt
Sent: Tuesday, December 03, 2019 09:05
To: TCC mailing list
Subject: [Tinycc-devel] make tcc reentrant

Hi all.

i try to write a lua binding for tcc. To work out propperly, the tcc lib
needs to be reentrant.

I took a look into the sources and found some comments (XXX:...) and
started with removing

the static var tcc_state. As a result allmost all lib functions needs a
1st parameter of

type TCCState*. I did this in my own local branch and tcc is still
running :).

But this is a really HUGE change. in addition most of the local vars in
tccpp, tccgen, ... needs

to be moved to TCCState. I can do that but at some points i will have
some questions and i

can only test on windows and probably on linux.

My 1st question is: Are you interested in these changes or should i do
this locally?

I would like to this together with you.



Tinycc-devel mailing list

Tinycc-devel mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]