On May 15, 2026 8:26:23 AM UTC, Mounir IDRASSI <[email protected]> wrote: >That being said, on Windows the old path still changes page protection on CRT >heap memory. > >Microsoft VirtualProtect documentation recommends avoiding this for >heap-allocated blocks, and documents VirtualAlloc + VirtualProtect as the >normal pattern for generated code. > > >So using VirtualAlloc avoids that pattern and is more in line with the Windows >API guidance.
Sure, but less in line with using same code for all platforms if possible TCC guidance ;) At least using VirtualAlloc would bypass the tcc_set_realloc() API. In that regard using same code did have a benefit. Anyway, I still wonder whether it was an actual problem or annoyance with using tcc in combination with that software? -- gr > > >Regards, > >Mounir IDRASSI _______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
