Bug#210598: libc6.1: Operations on subnormal floating-point numbers generate a floating point exception

2003-09-13 Thread Vincent Lefevre
On 2003-09-12 21:43:57 -0400, Daniel Jacobowitz wrote: This is not a glibc problem. It's not the call to fprintf which is faulting. It's the addition of 1.0 to a denormal. I know, but I thought that either the subnormals should have been treated in software by the libc, or the ldexp function

Bug#210598: libc6.1: Operations on subnormal floating-point numbers generate a floating point exception

2003-09-13 Thread Daniel Jacobowitz
On Sat, Sep 13, 2003 at 10:21:39AM +0200, Vincent Lefevre wrote: On 2003-09-12 21:43:57 -0400, Daniel Jacobowitz wrote: This is not a glibc problem. It's not the call to fprintf which is faulting. It's the addition of 1.0 to a denormal. I know, but I thought that either the subnormals

Bug#210598: libc6.1: Operations on subnormal floating-point numbers generate a floating point exception

2003-09-13 Thread Vincent Lefevre
reassign 210598 gcc-3.2 thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Processed: Bug#210598: libc6.1: Operations on subnormal floating-point numbers generate a floating point exception

2003-09-13 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: reassign 210598 gcc-3.2 Bug#210598: libc6.1: Operations on subnormal floating-point numbers generate a floating point exception Bug reassigned from package `libc6.1' to `gcc-3.2'. thanks Stopping processing here. Please contact me if you need

Bug#210598: libc6.1: Operations on subnormal floating-point numbers generate a floating point exception

2003-09-12 Thread Vincent Lefevre
Package: libc6.1 Version: 2.3.1-16 Severity: normal Consider the following program: #include stdio.h #include math.h int main (void) { double x = ldexp (1.0, -1038); fprintf (stderr, %g\n, x); fprintf (stderr, %g\n, x + 1.0); return 0; } When compiled and run, I get: $ ./tst

Bug#210598: libc6.1: Operations on subnormal floating-point numbers generate a floating point exception

2003-09-12 Thread Daniel Jacobowitz
On Fri, Sep 12, 2003 at 02:15:30PM +0200, Vincent Lefevre wrote: Package: libc6.1 Version: 2.3.1-16 Severity: normal Consider the following program: #include stdio.h #include math.h int main (void) { double x = ldexp (1.0, -1038); fprintf (stderr, %g\n, x); fprintf (stderr,

Bug#210598: libc6.1: Operations on subnormal floating-point numbers generate a floating point exception

2003-09-12 Thread Daniel Jacobowitz
On Sat, Sep 13, 2003 at 12:08:06AM +0200, Vincent Lefevre wrote: On 2003-09-12 14:39:40 -0400, Daniel Jacobowitz wrote: That's life on Alpha. I believe you can get different behavior by compiling with -mieee, does that work? That works, but IEEE-754 isn't the only standard. The ISO C

Bug#210598: libc6.1: Operations on subnormal floating-point numbers generate a floating point exception

2003-09-12 Thread Vincent Lefevre
On 2003-09-12 18:35:21 -0400, Daniel Jacobowitz wrote: I.E. without -mieee denormalized numbers are not completely supported. If they are not completely supported, the libc shouldn't generate them (to avoid FPE signals when results of libc functions are used in input of other operations).

Bug#210598: libc6.1: Operations on subnormal floating-point numbers generate a floating point exception

2003-09-12 Thread Vincent Lefevre
On 2003-09-12 14:39:40 -0400, Daniel Jacobowitz wrote: That's life on Alpha. I believe you can get different behavior by compiling with -mieee, does that work? That works, but IEEE-754 isn't the only standard. The ISO C standard has its own requirements. In my case, there was neither an

Bug#210598: libc6.1: Operations on subnormal floating-point numbers generate a floating point exception

2003-09-12 Thread Daniel Jacobowitz
On Sat, Sep 13, 2003 at 01:00:23AM +0200, Vincent Lefevre wrote: On 2003-09-12 18:35:21 -0400, Daniel Jacobowitz wrote: I.E. without -mieee denormalized numbers are not completely supported. If they are not completely supported, the libc shouldn't generate them (to avoid FPE signals when