This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: glibc segfault on "special" long double values is _ok_!?


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stop this nonsense discussion.  Intel's IA-64 people (and I smell HP in
there) are the idiots who caused this.  Talk to them.  If the work
around wouldn't be as simple as Jakub suggested I'd leave it as is.
Garbage in, whatever out, including crashes.  The numbers are completely
invalid and cannot happen in a regular program with a correct
implementation.  Here it's the implementation of the processor which is
at fault.  Neither CPU nor kernel bugs will be worked around if it's
expensive.  Just don't use those OS and processor versions if it bothers
you.

- --
â Ulrich Drepper â Red Hat, Inc. â 444 Castro St â Mountain View, CA â
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFGZ0LC2ijCOnn/RHQRAgb1AJ4lsvX5Y0+SMI+n6aWjNOlYhPxUegCdFqFw
U/edo9EcRfHH62XpKundF+4=
=OG+c
-----END PGP SIGNATURE-----


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]