This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: Latest 64 bit test stuff on sourceware
2013/2/18 Andy Koppe schrieb:
> On 18 February 2013 11:44, Corinna Vinschen wrote:
>> On Feb 17 10:37, Corinna Vinschen wrote:
>>> On Feb 16 22:47, Ken Brown wrote:
>>> > On 2/16/2013 5:17 PM, Peter Rosin wrote:
>>> > >3. The config.status scripts generated by the configure scrips
>>> > >I have tested are not working (all Makefiles end up empty), but
>>> > >I suspect that's some issue between autoconf and dash. So far it
>>> > >has worked to run ./config.status from plain old non-64-cygwin
>>> > >between configure and make.
>>> >
>>> > I made a first attempt to build emacs. I had the same problem as
>>> > Peter with all Makefiles being empty. In addition, the configure
>>>
>>> Yup, confirmed. Looks like a gawk thingy.
>>
>> Baaaaaad bug in Cygwin. The ReadFile OS function expects a pointer to
>> a DWORD variable (always 4 byte) to return the number of bytes read.
>> Cygwin provides a pointer to a size_t variable (4 bytes on i686, 8 bytes
>> on x86_64). Given the lots of scenarios in which this core function
>> is used, it's a miracle that other applications worked at all.
>>
>> I'm curious how many of these little buggers still lurk in the code...
>
> Shouldn't the compiler catch that sort of error?
>
> Andy
Well, it does in general. But of course if you are casting here
explicit to LPDWORD, it doesn't claim anything. Nevertheless it is an
error, and I think at least a strict-aliasing warning should be
emitted here.
Kai