[Bug c++/58059] g++: internal compiler error: Segmentation fault (program cc1plus)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58059 Felix Janda changed: What|Removed |Added CC||felix.janda at posteo dot de --- Comment #5 from Felix Janda --- Created attachment 37031 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37031&action=edit Simplified preprocessed output Can confirm with gentoo's gcc 4.9.3 on arm.
[Bug c/68866] New: ICE in set_lattice_value, at tree-ssa-cpp.c:490
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68866 Bug ID: 68866 Summary: ICE in set_lattice_value, at tree-ssa-cpp.c:490 Product: gcc Version: 4.9.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: felix.janda at posteo dot de Target Milestone: --- Minimal test case (containing invalid code): static char *a[] = {""}; int main(void) { for(int i=1;i<2;i++) if(a[i]) break; } The same error was already observed in http://www.openwall.com/lists/musl/2013/11/07/14
[Bug c/65958] [arm] -fstack-check breaks __builtin(alloca)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65958 --- Comment #2 from Felix Janda --- Actually I can hit this issue also with sh4 and microblaze. The test program needs to be modified slightly: int main(void) { char *p; if(1) { char i[48]; p = __builtin_alloca(8); p[0] = 1; } if(1) { char i[48] , j[64]; j[52] = 0; } return !p[0]; }
[Bug c/65958] New: -fstack-check breaks __builtin(alloca)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65958 Bug ID: 65958 Summary: -fstack-check breaks __builtin(alloca) Product: gcc Version: 4.9.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: felix.janda at posteo dot de Target Milestone: --- Target: arm On arm, gcc-4.9.2 compiles the following snippet to a program which returns 1 instead of 0 when the option -fstack-check is given. int main(void) { char *p; if(1) { char i[48]; p = __builtin_alloca(8); p[0] = 1; } if(1) { char i[48], j[64]; j[48] = 0; } return !p[0]; } I could reproduce the behavior already with gcc-4.7.1. The issue causes miscompilation of bash's lib/glob/glob.c. See: https://bugs.gentoo.org/show_bug.cgi?id=518598