[Bug c++/55340] New: Invalid maybe unitialized warning

2012-11-15 Thread jwillemsen at remedy dot nl
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55340 Bug #: 55340 Summary: Invalid maybe unitialized warning Classification: Unclassified Product: gcc Version: 4.7.1 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug c++/55340] Invalid maybe unitialized warning

2012-11-15 Thread jwillemsen at remedy dot nl
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55340 --- Comment #1 from Johnny Willemsen jwillemsen at remedy dot nl 2012-11-15 14:17:38 UTC --- Lowering optimization from -O3 to -O2 removes the warning

[Bug c++/55340] Invalid maybe unitialized warning

2013-02-27 Thread jwillemsen at remedy dot nl
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55340 --- Comment #3 from Johnny Willemsen jwillemsen at remedy dot nl 2013-02-27 19:20:24 UTC --- Thanks for checking this, will also try 4.8.0 at some point. We have hundreds of tests using C++11 extensively and this was the only one exposing

[Bug c++/50370] [C++0x] Multiple declarations with default template arguments accepted

2013-09-16 Thread jwillemsen at remedy dot nl
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50370 Johnny Willemsen jwillemsen at remedy dot nl changed: What|Removed |Added CC||jwillemsen

[Bug tree-optimization/42871] [4.4 Regression] g++: Internal error: Segmentation fault (program cc1plus)

2010-02-13 Thread jwillemsen at remedy dot nl
--- Comment #15 from jwillemsen at remedy dot nl 2010-02-13 10:03 --- After doing a yum update on FC12 we found that FC12 now also has gcc 4.4.3-4 which also has this bug when compiling ACE -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42871

[Bug c++/49252] New: Problem with inline

2011-06-01 Thread jwillemsen at remedy dot nl
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49252 Summary: Problem with inline Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassig...@gcc.gnu.org

[Bug c++/49450] New: not possible to call explicit destructor of std::string

2011-06-17 Thread jwillemsen at remedy dot nl
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49450 Summary: not possible to call explicit destructor of std::string Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug c++/49450] not possible to call explicit destructor of std::string

2011-06-17 Thread jwillemsen at remedy dot nl
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49450 --- Comment #1 from Johnny Willemsen jwillemsen at remedy dot nl 2011-06-17 11:32:51 UTC --- g++-4.6 (SUSE Linux) 4.6.0 20110505 [gcc-4_6-branch revision 173419] Copyright (C) 2011 Free Software Foundation, Inc. This is free software; see

[Bug c++/49450] not possible to call explicit destructor of std::string

2011-06-17 Thread jwillemsen at remedy dot nl
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49450 Johnny Willemsen jwillemsen at remedy dot nl changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug c++/49450] not possible to call explicit destructor of std::string

2011-06-17 Thread jwillemsen at remedy dot nl
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49450 Johnny Willemsen jwillemsen at remedy dot nl changed: What|Removed |Added Resolution|FIXED |INVALID