From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12020 invoked by alias); 20 Feb 2012 09:29:25 -0000 Received: (qmail 12010 invoked by uid 22791); 20 Feb 2012 09:29:24 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 20 Feb 2012 09:28:37 +0000 From: "rguenther at suse dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/51782] -ftree-sra: Missing address-space information leads to wrong Date: Mon, 20 Feb 2012 09:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Keywords: addr-space, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenther at suse dot de X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jamborm at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.7.0 X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2012-02/txt/msg01932.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51782 --- Comment #19 from rguenther at suse dot de 2012-02-20 09:27:48 UTC --- On Fri, 17 Feb 2012, jamborm at gcc dot gnu.org wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51782 > > --- Comment #17 from Martin Jambor 2012-02-17 17:59:43 UTC --- > Created attachment 26695 > --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26695 > Untested proposed fix > > This untested patch fixes the issue for me on a cross-compiler. It > would be great if someone who is set up to run the testsuite on a > platform with multiple address spaces or a simulator of one could test > it a bit. > > My plan is to discuss this with maintainers next week and if they like > the approach, give it a formal bootstrap and test run on x86_64 and > submit shortly thereafter if everything goes fine. base returned from get_base_address should never be NULL, so it's safe to assume it isn't. Otherwise the patch looks ok to me. Richard.