[Bug libstdc++/10606] uncaught_exception() returns false too early

2005-02-18 Thread david dot moore at intel dot com
--- Additional Comments From david dot moore at intel dot com 2005-02-18 17:56 --- As the person who has been working on similar problems in the Intel Compiler, Martin and I had some lengthy discussions about this during which he convinced me he was correct. The result was issue 475

[Bug libstdc++/20431] New: Out of range float inputs to cin get spurious values

2005-03-11 Thread david dot moore at intel dot com
Large values (that should produce inf, produce a bogus result instead. For example, 1.0e+309 produces 1.39065e-309 on gcc 3.4.3! Here is the trivial program: #include #include using namespace std; int main() { double a,b; cout << "Enter a (Using cin):"; cin >> a; printf ("Enter b (

[Bug libstdc++/20433] New: Out of range float inputs to cin get spurious values

2005-03-11 Thread david dot moore at intel dot com
Large values (that should produce inf, produce a bogus result instead. For example, 1.0e+309 produces 1.39065e-309 on gcc 3.4.3! Here is the trivial program: #include #include using namespace std; int main() { double a,b; cout << "Enter a (Using cin):"; cin >> a; printf ("Enter b (

[Bug libstdc++/20433] Out of range float inputs to cin get spurious values

2005-03-11 Thread david dot moore at intel dot com
--- Additional Comments From david dot moore at intel dot com 2005-03-11 21:39 --- Oops - this happened when I hit refresh to see Paulo's comments. Instead it resubmitted the bug! Very strange. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20433

[Bug c++/24559] New: Incorrect definition of wcspbrk in cwchar

2005-10-27 Thread david dot moore at intel dot com
: unassigned at gcc dot gnu dot org ReportedBy: david dot moore at intel dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24559

[Bug middle-end/22275] [3.4/4.0/4.1/4.2 Regression] bitfield layout change

2006-02-10 Thread david dot moore at intel dot com
--- Comment #45 from david dot moore at intel dot com 2006-02-10 22:34 --- The (C99) standard says: 6.7.2.1 (10) An implementation may allocate any addressable storage unit large enough to hold a bitfield. and 6.7.2.1 (11) As a special case, a bit-field structure member with a width

[Bug middle-end/22275] [3.4/4.0/4.1/4.2 Regression] bitfield layout change

2006-02-10 Thread david dot moore at intel dot com
--- Comment #46 from david dot moore at intel dot com 2006-02-11 00:14 --- (Note - I had not realized the importance of pragma pack to this problem. The fact that without it the behavior has not changed weakens my case, although it probably weakens the case that it should be restored

[Bug libstdc++/19284] New: Simple type names fail to demangle - regression from 3.2

2005-01-05 Thread david dot moore at intel dot com
Summary: Simple type names fail to demangle - regression from 3.2 Product: gcc Version: 3.4.3 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libstdc++ AssignedTo: unassigned at gcc dot gnu dot org Report

[Bug libstdc++/19284] Simple type names fail to demangle - regression from 3.2

2005-01-05 Thread david dot moore at intel dot com
--- Additional Comments From david dot moore at intel dot com 2005-01-05 23:55 --- Created an attachment (id=7881) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=7881&action=view) Test case attached (same as pasted version) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19284

[Bug libstdc++/19284] Simple type names fail to demangle - regression from 3.2

2005-01-05 Thread david dot moore at intel dot com
--- Additional Comments From david dot moore at intel dot com 2005-01-06 00:08 --- Subject: RE: Simple type names fail to demangle - regression from 3.2 Is that in gnats? Actually, my real question is should I have reported this in a different data base? Searched for demangle and did