From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15074 invoked by alias); 13 Nov 2008 17:28:54 -0000 Received: (qmail 2066 invoked by uid 48); 13 Nov 2008 17:27:32 -0000 Date: Thu, 13 Nov 2008 17:28:00 -0000 Message-ID: <20081113172732.2065.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug target/38052] [4.4 Regression] genautomata segfaults when -O2 is enabled In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "r0bertz at gentoo dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2008-11/txt/msg00983.txt.bz2 ------- Comment #5 from r0bertz at gentoo dot org 2008-11-13 17:27 ------- I am trying to find which specific flag or flags when used together with -foptimize-sibling-calls could trigger this problem. As the first step I tried to find a set of flags used together with -O0 and -foptimize-sibling-calls could trigger this problem. Presumably this set of flags should be those disabled at -O0 but enabled at -O1. So I did the following to find the differences: gcc -c -Q -O0 --help=optimizers > /tmp/O0-opts gcc -c -Q -O1 --help=optimizers > /tmp/O1-opts diff /tmp/O0-opts /tmp/O1-opts | grep enabled | cut -d " " -f 4 Then I used these flags with -O0 and -foptimize-sibling-calls together, but this didn't trigger the bug. Is there anything I have overlooked here? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38052