From owner-freebsd-stable@FreeBSD.ORG Sat Mar 22 18:39:27 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8BAA21065672 for ; Sat, 22 Mar 2008 18:39:27 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CF4CB8FC18; Sat, 22 Mar 2008 18:39:26 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47E55264.2030004@FreeBSD.org> Date: Sat, 22 Mar 2008 19:39:32 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213) MIME-Version: 1.0 To: Mikael Ikivesi References: <20080322192433.3719eb44@pp.inet.fi> In-Reply-To: <20080322192433.3719eb44@pp.inet.fi> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: gcc -O2 error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Mar 2008 18:39:27 -0000 Mikael Ikivesi wrote: > Hi > > I am running uptodate RELENG_7. It has gcc (GCC) 4.2.1 20070719 > [FreeBSD]. > > I tried to track down segfaults from my code and I accidentaly found a > optimization error. Code did not segfault when compiled without > optimization but crashed when -O2 was used. > > I tried to track it I could make the gcc give me following error by > simply stripping few lines: > > ----------------------- > wrong.c: In function 'wrong': > wrong.c:11: error: Attempt to delete prologue/epilogue insn: > (insn/f 47 46 48 2 (set (mem:SI (plus:SI (reg/f:SI 6 bp) > (const_int -8 [0xfffffffffffffff8])) [0 S4 A8]) > (reg:SI 3 bx)) -1 (nil) > (nil)) > wrong.c:11: internal compiler error: in propagate_one_insn, at > flow.c:1735 Please submit a full bug report, > with preprocessed source if appropriate. > See for instructions. So, did you consider perhaps following this advice? ;-) Kris