From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-273357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 10046 invoked by alias); 20 Jan 2009 03:50:17 -0000
Received: (qmail 10021 invoked by uid 48); 20 Jan 2009 03:50:06 -0000
Date: Tue, 20 Jan 2009 03:50:00 -0000
Subject: [Bug rtl-optimization/38921]  New: [4.3 Regression] NULL access in delay-slot
X-Bugzilla-Reason: CC
Message-ID: <bug-38921-507@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "hp at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2009-01/txt/msg02159.txt.bz2

With 4.3 branch at revision 143494 (probably also at least 135713, but that has
local patches I don't care to revert to verify) the attached code puts the
p->next load in the delay-slot of the NULL-check branch, yielding a NULL
access.
I'm guessing a reorg.c bug...

(It doesn't seem to happen at HEAD/4.4 at 143507 which instead has some weird
and suboptimal cross-jumping behavior.)


-- 
           Summary: [4.3 Regression] NULL access in delay-slot
           Product: gcc
           Version: 4.3.3
            Status: UNCONFIRMED
          Keywords: wrong-code
          Severity: normal
          Priority: P3
         Component: rtl-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: hp at gcc dot gnu dot org
  GCC host triplet: x86_64-unknown-linux-gnu, i686-unknown-linux-gnu
GCC target triplet: cris-*-* and crisv32-*-*


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38921