From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3927 invoked by alias); 1 Mar 2013 11:00:59 -0000 Received: (qmail 3703 invoked by uid 48); 1 Mar 2013 11:00:21 -0000 From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/56483] LTO issue with expanding GIMPLE_COND Date: Fri, 01 Mar 2013 11:00:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Keywords: lto, missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Status Keywords Last reconfirmed Component AssignedTo Ever Confirmed 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: 2013-03/txt/msg00030.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56483 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Keywords| |lto, missed-optimization Last reconfirmed| |2013-03-01 Component|lto |middle-end AssignedTo|unassigned at gcc dot |rguenth at gcc dot gnu.org |gnu.org | Ever Confirmed|0 |1 --- Comment #2 from Richard Biener 2013-03-01 11:00:18 UTC --- gimple_cond_single_var_p should be inlined at its single caller, it isn't any good abstraction. integer_zerop isn't a good enough test for what the single caller tries to assert as far as I can see. You'd need to test whether it's precision is 1 as well (or whether it's BOOLEAN_TYPE). The IR reader cannot be fixed (the middle-end shouldn't use frontend boolean_*_node) - frontends have different representation for their boolean_{true,false,type}_nodes. Well. Confirmed and mine.