No, it wouldn't help, as we still have an strict-aliasing issue. And additionally the upper 32-bit of object are containing random values
Kai 2014-11-04 17:36 GMT+01:00 Martell Malone <martellmal...@gmail.com>: > Yes I agree with this. > Especially because lfind is dynamically linked to msvcrt > > We didn't into this before on irc but > > could we add something similar to this in header in mingw64 > #define _lfind(a,b,c,d,e) _lfind(a,b,(unsigned int*)c,d,e) > > Which explicitly casts it to (unsigned int *) > > Would this solve anything > ? > > Many Thanks > Martell > > On Tue, Nov 4, 2014 at 4:17 PM, Kai Tietz <ktiet...@googlemail.com> wrote: >> >> Issue here is that referenced object 'unsigned int' has different size >> to 'size_t' on Windows. Means that function might set only lower >> 32-bit to something meaningful, and so passing a size_t pointer to it >> could lead to corrupted value in it. >> >> Kai ------------------------------------------------------------------------------ _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
