From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25970 invoked by alias); 17 Mar 2003 15:26:03 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 25939 invoked by uid 71); 17 Mar 2003 15:26:02 -0000 Date: Mon, 17 Mar 2003 15:26:00 -0000 Message-ID: <20030317152602.25938.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Falk Hueffner Subject: Re: optimization/8300: [3.2/3.3/3.4 regression] [sparc] ICE in gen_reg_rtx, at emit-rtl.c:662 Reply-To: Falk Hueffner X-SW-Source: 2003-03/txt/msg01139.txt.bz2 List-Id: The following reply was made to PR optimization/8300; it has been noted by GNATS. From: Falk Hueffner To: Robert Schiele Cc: Richard Henderson , gcc-bugs@gcc.gnu.org, tneumann@pi3.informatik.uni-mannheim.de, gcc-gnats@gcc.gnu.org Subject: Re: optimization/8300: [3.2/3.3/3.4 regression] [sparc] ICE in gen_reg_rtx, at emit-rtl.c:662 Date: 17 Mar 2003 16:24:34 +0100 Robert Schiele writes: > How about this: > > void a() { > double b; > int c[2]; > *((int*)&b) && (c[1] = 0); > } > > Exactly same problem. And this time there is no pointer outside well > defined data area. You agree that this sample is legal code? No, you're violating the rule in 6.5.7 by accessing an object of type double with an lvalue of type int. -- Falk