On Thu, 2 Jan 2025, Pali Rohár wrote:
I see. But if we change the default value again then it would be
necessary to updates also mingw-w64 headers with new check for system
msvcrt.dll value. Something what I wrote above (just first two cases).
Yes - we could change that in any case, to allow any value between 0x600 and
0x6FF, in case users override it.
Then for our default value; either 0x0601 or 0x06FF would be ok with me. At
this point, I'm actually leaning towards 0x06FF.
This makes it clearer that it's not specifically the 2k/Me version (not ==
0x0601), and that it's "almost" the 0x0700 that we had before (even if that
"almost" wouldn't functionally have any effect anywhere). With 0x06FF we
would get the right behaviour if there's any condition which is "> 0x0601"
(not sure if that one exists anywhere though).
This makes sense. Better to use 0x06FF.
Did anything more come out of this?
The change that we did is disruptive, at least for some users. I think
there wasn't any opposition to switching to 0x6ff instead of 0x600, for
the msvcrt.dll case, which at least should avoid some cases of surprises,
even if it doesn't avoid every single case?
// Martin
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
