[Bug other/61427] New: Fail to build due to #error GATHER_STATISTICS must be defined

2014-06-05 Thread Torsten at Robitzki dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61427 Bug ID: 61427 Summary: Fail to build due to #error GATHER_STATISTICS must be defined Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal

[Bug c++/61421] Invalid -O2 optimization breaks program

2014-06-05 Thread mimamer at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61421 --- Comment #18 from mimamer at gmail dot com --- Ah? I didn't figure that was allowed per strict aliasing rules. But it still doesn't solve one problem: inline T *dequeue() { node *head = anchor.next; anchor.next = head-next;

[Bug libstdc++/61424] std::regex matches right to left, not leftmost longest

2014-06-05 Thread timshen at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61424 --- Comment #2 from Tim Shen timshen at gcc dot gnu.org --- Sorry, the preference of results of | is actually arbitrary. I'll fix it later.

[Bug other/61427] Fail to build due to #error GATHER_STATISTICS must be defined

2014-06-05 Thread Torsten at Robitzki dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61427 --- Comment #1 from Torsten Robitzki Torsten at Robitzki dot de --- I've tried the same configuration with gcc 4.8.3. The same error occurs in the config.log, but this time the build stops with: g++ -I../../libcpp -I. -I../../libcpp/../include

[Bug c/53119] -Wmissing-braces wrongly warns about universal zero initializer {0}

2014-06-05 Thread nightstrike at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53119 nightstrike nightstrike at gmail dot com changed: What|Removed |Added CC||nightstrike at

[Bug c/53119] -Wmissing-braces wrongly warns about universal zero initializer {0}

2014-06-05 Thread bugdal at aerifal dot cx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53119 --- Comment #14 from Rich Felker bugdal at aerifal dot cx --- In C++, the correct zero initializer is {}, not {0}. I'm not an expert in C++ but I think {0} in C++ might even be a constraint violation unless the brace level happens to match.

[Bug target/61300] powerpc64le miscompile with KR-style function definition at -O0

2014-06-05 Thread amodra at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61300 --- Comment #8 from Alan Modra amodra at gcc dot gnu.org --- Author: amodra Date: Fri Jun 6 01:04:22 2014 New Revision: 211296 URL: http://gcc.gnu.org/viewcvs?rev=211296root=gccview=rev Log: PR target/61300 * doc/tm.texi.in

[Bug middle-end/56574] False possibly uninitialized variable warning

2014-06-05 Thread luto at mit dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56574 Andy Lutomirski luto at mit dot edu changed: What|Removed |Added CC||luto at mit dot edu

[Bug c/53119] -Wmissing-braces wrongly warns about universal zero initializer {0}

2014-06-05 Thread mpolacek at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53119 Marek Polacek mpolacek at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

<    1   2