Re: [Tinycc-devel] problem on win64 with latest commit

2024-02-29 Thread Herman ten Brugge via Tinycc-devel
On 2/29/24 23:17, grischka wrote: On 29.02.2024 07:26, Herman ten Brugge via Tinycc-devel wrote: Setting CONFIG_RUNMEM_RO=0 looks incorrect to me because it sets write in executables. Apple has implemented W^X (Writes can not occur in executables) for security reasons. This may also be

Re: [Tinycc-devel] problem on win64 with latest commit

2024-02-29 Thread grischka via Tinycc-devel
On 29.02.2024 07:26, Herman ten Brugge via Tinycc-devel wrote: Setting CONFIG_RUNMEM_RO=0 looks incorrect to me because it sets write in executables. Apple has implemented W^X (Writes can not occur in executables) for security reasons. This may also be implemented in in future linux/bsd

[Tinycc-devel] Re : Minimizing libtcc memory use

2024-02-29 Thread david . koch
Hi, isn't there a garbage collecting done at the end to remove all the unused stuff to produce a binary that contains only the necessary parts ? Regards. - Mail d'origine - De: Eric Raible À: tinycc-devel@nongnu.org Envoyé: Thu, 29 Feb 2024 08:43:17 +0100 (CET) Objet: [Tinycc-devel]

Re: [Tinycc-devel] problem on win64 with latest commit

2024-02-29 Thread Eric Raible
I cannot speak for Griska or the reasons why that change was committed. But with respect to my mail from 2/25, once again, all I was doing was hinting that tcc could be configured to not call (the since reverted) unportable APIs. Anyway, from my point of view, a default of RO=1 is fine. But it