From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30827 invoked by alias); 11 Feb 2015 16:32:10 -0000 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 Received: (qmail 30773 invoked by uid 48); 11 Feb 2015 16:32:05 -0000 From: "jamborm at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/64835] -fno-ipa-cp is inconsitently supported when attributes optimize or target are used Date: Wed, 11 Feb 2015 16:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jamborm at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jamborm at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to everconfirmed Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-02/txt/msg01213.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64835 Martin Jambor changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2015-02-11 CC| |jamborm at gcc dot gnu.org Assignee|unassigned at gcc dot gnu.org |jamborm at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Martin Jambor --- The problem is that in the testcase iinline-1.c as it is in the testsuite, we use -fno-ipa-cp on the command line so that the interprocedural phase of IPA-CP is not run so that it does not interfere with the interprocedural stage of inlining, which however uses information gathered by the function body analysis of ipa-prop (which is invoked by both IPA-CP and inlining). However, when we inspect the function specific optimizations in ipa-prop at this stage, we bail out if we see -fno-ipa-cp. So yes, there is a clear inconsistency, but at the same time, having the ability to switch off only the interprocedural part of IPA-CP is extremely convenient for testing how the inliner uses jump functions and other stuff gathered by ipa-prop. I'll try to come up with some fix.