http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48211
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-invalid-code
Status|UNCONFIRMED |NEW
Last reconfirmed| |2011.05.03 21:00:51
Known to work| |4.5.2, 4.6.0
Summary|[C++0x] Segment Fault When |[4.7 Regression] [C++0x]
|Compiling |Segment Fault When
| |Compiling
Ever Confirmed|0 |1
Known to fail| |4.7.0
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-05-03
21:00:51 UTC ---
I can confirm this with the 4.7-20110430 snapshot, but only on i686 not x86_64
The code in comment 2 gets a segfault here:
Program received signal SIGSEGV, Segmentation fault.
0x08336684 in ggc_set_mark (p=0xb6f7a878) at
../../gcc-4.7-20110430/gcc/ggc-page.c:1333
1333 if (entry->in_use_p[word] & mask)
(gdb) p entry
$1 = (page_entry *) 0x9014f48
(gdb) p word
$2 = 8699297
(gdb) p entry->in_use_p
$3 = {4293918719}
Valgrind shows lots of errors in cpp. The code is not valid, I don't know if
the ICE also happens with a fixed version.
The code in comment 1 does not ICE
