--- Comment #8 from pcarlini at suse dot de 2007-11-26 18:26 ---
Fixed for 4.3.0.
--
pcarlini at suse dot de changed:
What|Removed |Added
Status|ASSIGNED
--- Comment #7 from paolo at gcc dot gnu dot org 2007-11-26 18:25 ---
Subject: Bug 25913
Author: paolo
Date: Mon Nov 26 18:24:54 2007
New Revision: 130443
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=130443
Log:
2007-11-26 Paolo Carlini <[EMAIL PROTECTED]>
PR libstd
--
pcarlini at suse dot de changed:
What|Removed |Added
AssignedTo|unassigned at gcc dot gnu |pcarlini at suse dot de
|dot org |
--- Comment #6 from pinskia at gcc dot gnu dot org 2006-01-23 14:50 ---
Confirmed.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Status|UNCON
--- Comment #5 from gdr at cs dot tamu dot edu 2006-01-22 21:17 ---
Subject: Re: Client's isnormal function is broken by cmath
"hhinnant at apple dot com" <[EMAIL PROTECTED]> writes:
| (In reply to comment #3)
|
| > (3) even when isnormal is enable-if hacked, you still potentially
--- Comment #4 from hhinnant at apple dot com 2006-01-22 20:49 ---
(In reply to comment #3)
> (3) even when isnormal is enable-if hacked, you still potentially
> run into the same problem.
For example?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25913
--- Comment #3 from gdr at cs dot tamu dot edu 2006-01-22 20:42 ---
Subject: Re: Client's isnormal function is broken by cmath
"hhinnant at apple dot com" <[EMAIL PROTECTED]> writes:
| (In reply to comment #1)
| >
| > Does the problem exist if you configure with --disable-c99?
|
| I
--- Comment #2 from hhinnant at apple dot com 2006-01-22 20:25 ---
(In reply to comment #1)
>
> Does the problem exist if you configure with --disable-c99?
I haven't tried that configuration. The docs say that setting may change
libstdc++'s ABI.
So this is expected behavior for the d
--- Comment #1 from gdr at cs dot tamu dot edu 2006-01-22 20:10 ---
Subject: Re: New: Client's isnormal function is broken by cmath
"hhinnant at apple dot com" <[EMAIL PROTECTED]> writes:
| I believe the program below should compile:
Does the problem exist if you configure with --di
