[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: glibc segfault on "special" long double values is _ok_!?
From: |
Bruno Haible |
Subject: |
Re: glibc segfault on "special" long double values is _ok_!? |
Date: |
Thu, 7 Jun 2007 04:09:06 +0200 |
User-agent: |
KMail/1.5.4 |
Ulrich Drepper wrote:
> Intel's IA-64 people (and I smell HP in there) are the idiots who caused this.
The crash also occurs on i386 platforms, e.g. CPUs built by AMD.
> Here it's the implementation of the processor which is at fault.
But printf %Le does not do any hardware floating-point instruction except
those in glibc's __isnanl and __isinfl functions: __mpn_extract_long_double
extracts the bits using integer arithmetic.
> Neither CPU nor kernel bugs will be worked around if it's expensive.
Do you find that Jakub's added 4 lines of code are "expensive"?
> Just don't use those OS and processor versions if it bothers you.
Right. Don't use i386, x86_64, and ia64. What machine are you using?
Bruno
Re: glibc segfault on "special" long double values is _ok_!?, Paul Mackerras, 2007/06/06
Re: glibc segfault on "special" long double values is _ok_!?, Bruno Haible, 2007/06/06
[PATCH] Re: glibc segfault on "special" long double values is _ok_!?, Jakub Jelinek, 2007/06/06
Re: glibc segfault on "special" long double values is _ok_!?, Jeremy Linton, 2007/06/07
arch-independent glibc printf segfault for "special" long double values, Jim Meyering, 2007/06/08