Yes! On Wed, 11 Dec 2019, grischka wrote:
> Couldn't help to try out some things, related to the matter. > See > https://repo.or.cz/tinycc.git/commitdiff/72729d8e360489416146d6d4fd6bc57c9c72c29b -- karl On Wed, Dec 11, 2019 at 5:43 AM grischka <gris...@gmx.de> wrote: > > Ulrich Schmidt wrote: > > Am 11.12.2019 um 03:58 schrieb grischka: > >> > >> With multi-threading though, the underlying machine tcc code, should > >> account for > >> side effects of the shared execution space, so adds even a tiny bit > >> (and with the > >> best of efforts) of complexity. So that is not quite primitive and it > >> seems like > >> a condradiction with the "direct access to the machine" thing. It's > >> even is a bit > >> of odd, that tcc which is a C compiler, to use "second thoughts" in > >> its C code. > > > Noone suggest multitreading. I was talking about makeing libtcc > > reentrant. Maybe i was unclear in the subject line. > > It was not me who wrote that but reentrancy should work now. > Hope it will help your plans, keep us informed. ;) > > --- grischka > > > _______________________________________________ > 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
