On Linux/x86-64, revision 161806 gave: # /usr/bin/valgrind --tool=memcheck build/genautomata /export/gnu/import/svn/gcc-test/src-trunk/gcc/config/i386/i386.md insn-conditions.md > /dev/null ==5903== Memcheck, a memory error detector ==5903== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. ==5903== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info ==5903== Command: build/genautomata /export/gnu/import/svn/gcc-test/src-trunk/gcc/config/i386/i386.md insn-conditions.md ==5903== ==5903== Invalid read of size 8 ==5903== at 0x401BE7: check_absence_pattern_sets (genautomata.c:4353) ==5903== by 0x40D85F: create_automata (genautomata.c:3503) ==5903== by 0x4101D5: expand_automata (genautomata.c:9093) ==5903== by 0x4115B8: main (genautomata.c:9543) ==5903== Address 0x1c is not stack'd, malloc'd or (recently) free'd ==5903== ==5903== ==5903== Process terminating with default action of signal 11 (SIGSEGV) ==5903== Access not within mapped region at address 0x1C ==5903== at 0x401BE7: check_absence_pattern_sets (genautomata.c:4353) ==5903== by 0x40D85F: create_automata (genautomata.c:3503) ==5903== by 0x4101D5: expand_automata (genautomata.c:9093) ==5903== by 0x4115B8: main (genautomata.c:9543) ==5903== If you believe this happened as a result of a stack ==5903== overflow in your program's main thread (unlikely but ==5903== possible), you can try to increase the size of the ==5903== main thread stack using the --main-stacksize= flag. ==5903== The main thread stack size used in this run was 8388608. ==5903== ==5903== HEAP SUMMARY: ==5903== in use at exit: 11,187,082 bytes in 73,185 blocks ==5903== total heap usage: 83,419 allocs, 10,234 frees, 32,694,074 bytes allocated ==5903==
-- Summary: Stage2/stage3 genautomata has invalid memory access Product: gcc Version: 4.5.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: hjl dot tools at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44817