From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27958 invoked by alias); 26 Aug 2009 11:04:26 -0000 Received: (qmail 27820 invoked by uid 22791); 26 Aug 2009 11:04:25 -0000 X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_33,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-vw0-f174.google.com (HELO mail-vw0-f174.google.com) (209.85.212.174) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 26 Aug 2009 11:04:19 +0000 Received: by vws4 with SMTP id 4so25380vws.0 for ; Wed, 26 Aug 2009 04:04:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.107.131 with SMTP id b3mr4801790vcp.94.1251284656720; Wed, 26 Aug 2009 04:04:16 -0700 (PDT) In-Reply-To: References: <84fc9c000908180214x5f85c03ie8b3da8e4a713932@mail.gmail.com> <84fc9c000908180242t2993745frdda5aed9cbd5c178@mail.gmail.com> Date: Wed, 26 Aug 2009 16:37:00 -0000 Message-ID: <84fc9c000908260404w5721de63u30b2dd835a2e21e8@mail.gmail.com> Subject: Re: Trying to backport alias fix to 4.2 From: Richard Guenther To: Ned Gill Cc: gcc@gcc.gnu.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-08/txt/msg00473.txt.bz2 On Wed, Aug 26, 2009 at 12:50 PM, Ned Gill wrote: > > FWIW, I'm still looking at this on and off. =A0I beleive the pure functio= n was > a red herring, as this example also does the wrong thing: > > extern int z; > > int foo(int *y) > { > =A0 =A0z =3D 1; > =A0 =A0*y =3D 0; > =A0 =A0return z; =A0// returns 1, even though y could point to z :( > } > > Not much joy tracking it down as yet. =A0I've attached the alias informat= ion > tree dump in case anyone fancies a look. =A0It looks ok to me, but I don't > really understand it fully. > > As a reminder: this bug is fixed from r119502 on trunk. I'd like to fix it > on 4.2.x. Sorry, you are hitting some major latent problems there. The affected piece got a complete rewrite for 4.3, an isolated fix is likely not easily possible. The above problem is that NONLOCAL is broken - it should have used the SMT for anything instead. The code in 4.4 is somewhat sane, still corner cases are incorrect there, hopefully fixed on trunk. Richard. > > Ned. > > > -- >