From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11948 invoked by alias); 20 May 2003 00:56:01 -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 11925 invoked by uid 71); 20 May 2003 00:56:01 -0000 Date: Tue, 20 May 2003 00:56:00 -0000 Message-ID: <20030520005601.11921.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Dara Hazeghi Subject: Re: target/7462: [powerpc] Bad code for unalign access Reply-To: Dara Hazeghi X-SW-Source: 2003-05/txt/msg02129.txt.bz2 List-Id: The following reply was made to PR target/7462; it has been noted by GNATS. From: Dara Hazeghi To: Hans-Joachim Widmaier Cc: gcc-gnats@gcc.gnu.org Subject: Re: target/7462: [powerpc] Bad code for unalign access Date: Mon, 19 May 2003 17:54:37 -0700 (PDT) --- Hans-Joachim Widmaier wrote: > Dara Hazeghi: > > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- > > > trail&database=gcc&pr=7462 > > > > Hello, > > > > gcc 3.1.1 is a bit old, and a fair bit has changed > since then. Would it > > be possible for you to check whether this problem > is still present with > > gcc 3.3? Thanks, > > Hello, > > a quick test showed that gcc 3.3 indeed seems to do > that right. So that > bug can be closed. Alas, it creates new sections > which our link script doesn't > cater for, and a rebuild of the whole project raised > an internal compiler error. > Since I'm a bit tight on time, I will defer > investigating that further and > revert to gcc 3.2.2. Sorry to see that 3.3 brings new bugs! When you get a chance, please report the new problem you've found. Meanwhile we'll close this bug. Dara __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com