This is the mail archive of the
libc-hacker@cygnus.com
mailing list for the glibc project.
Re: Version 2.1.pre1 of the crypt extension
- To: Wolfram Gloger <wmglo@dent.med.uni-muenchen.de>
- Subject: Re: Version 2.1.pre1 of the crypt extension
- From: Zack Weinberg <zack@rabi.columbia.edu>
- Date: Fri, 26 Feb 1999 12:15:55 -0500
- cc: libc-hacker@cygnus.com, law@cygnus.com
On 26 Feb 1999 16:31:58 -0000, Wolfram Gloger wrote:
>Hello,
>
>> The change is a workaround for an egcs bug/omission that is only
>> visible on 32-bit machines when egcs was not built under glibc 2.1.
>>
>> You can check for the egcs problem by trying the following short
>> program:
>>
>> int main(void)
>> {
>> #if 4294967295U != 18446744073709551615ULL
>> return 0;
>> #else
>> abort();
>> #endif
>> }
>>
>> If it aborts, you know your egcs has the problem.
>
>All the egcs that I have compiled so far (none with glibc2.1 though),
>including one for mips-irix6, show this `problem', while SGI cc
>passes. So, is this really an egcs bug and has nothing to do with
>glibc ? If so, I'd like to report it as a bug to egcs-bugs, because
>egcs-1.1.2pre2 still shows the problem.
We've got this fixed now in development egcs. Jeff, you might want to
consider putting Kaveh's HOST_WIDEST_INT stuff into 1.1.2. The above
bug is causing a real problem with libc 2.1.
zw