From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13668 invoked by alias); 8 Oct 2005 22:19:59 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 13659 invoked by uid 48); 8 Oct 2005 22:19:57 -0000 Date: Sat, 08 Oct 2005 22:19:00 -0000 Message-ID: <20051008221957.13658.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug middle-end/24279] SEGV at reload.c:2400 with -O2 In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "shap at eros-os dot org" X-SW-Source: 2005-10/txt/msg01045.txt.bz2 List-Id: ------- Comment #5 from shap at eros-os dot org 2005-10-08 22:19 ------- The patch from PR 23043 does NOT resolve this. Same error, reported at the same place in reload.c. Given the number of other mode-related bugs against m68k, I was suspicious of that, but when I re-run under gdb, the value of val.start at the time of the fault is improbably high (1708), and then I get (gdb) p hard_regno_nregs[val.start] Cannot access memory at address 0x831b0d0 Not sure if this helps suggest anything. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24279