From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10446 invoked by alias); 9 Mar 2012 21:09:21 -0000 Received: (qmail 10437 invoked by uid 22791); 9 Mar 2012 21:09:20 -0000 X-SWARE-Spam-Status: No, hits=-2.8 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; Fri, 09 Mar 2012 21:09:08 +0000 From: "aldyh at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/52548] New: missed PRE optimization when function call follows to-be hoisted variable Date: Fri, 09 Mar 2012 21:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: aldyh at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: 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-03/txt/msg00764.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52548 Bug #: 52548 Summary: missed PRE optimization when function call follows to-be hoisted variable Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned@gcc.gnu.org ReportedBy: aldyh@gcc.gnu.org For the following code (for -O2): int flag, hoist, y, z; void foo (void) { if (flag) y = hoist + 4; else flag = 888; z = hoist + 4; bark (); } ...PRE should be moving "hoist + 4" to the else arm, but it fails to do so. If you remove the call to bark(), [hoist + 4] gets moved appropriately. The bark() function call is in the same basic block as "z = hoist + 4". I wild guess is that "hoist" isn't anticipatable at the *end* of the BB beginning with "z = hoist + 4". Splitting BB's at function calls may improve PRE. Just a guess...