From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22342 invoked by alias); 8 May 2009 20:34:40 -0000 Received: (qmail 22290 invoked by alias); 8 May 2009 20:34:28 -0000 Date: Fri, 08 May 2009 20:34:00 -0000 Message-ID: <20090508203428.22289.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug middle-end/39978] [4.5 Regression] SEGV compiling libiberty/regex.c in stage2 In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "dave at hiauly1 dot hia dot nrc dot ca" 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: 2009-05/txt/msg00712.txt.bz2 ------- Comment #10 from dave at hiauly1 dot hia dot nrc dot ca 2009-05-08 20:34 ------- Subject: Re: [4.5 Regression] SEGV compiling libiberty/regex.c in stage2 > Interesting you don't hit the bug I described in PR 40031. I tested the following in the regression search: 146971 bad 146908 bad 146900 bad 146894 bad 146893 ok 146892 ok 146876 ok 146845 ok The bug in PR 40031 was reported at 147121, so maybe things have changed. Dave -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39978