From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16554 invoked by alias); 12 Dec 2014 04:08:06 -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 16482 invoked by uid 48); 12 Dec 2014 04:07:57 -0000 From: "jasonwucj at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/64217] LRA: generate wrong liveness info after r217947 for clobber in jump_insn Date: Fri, 12 Dec 2014 04:08: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: jasonwucj at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jasonwucj at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc component 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: 2014-12/txt/msg01353.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64217 Chung-Ju Wu changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2014-12-12 CC| |jasonwucj at gcc dot gnu.org Component|rtl-optimization |target Assignee|unassigned at gcc dot gnu.org |jasonwucj at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #2 from Chung-Ju Wu --- (In reply to Vladimir Makarov from comment #1) > > So I'd add at least '=' but it is better to add '=r' or '= register constraint>' to solve the problem. > Thanks Kito for reporting this issue. Also thanks Vladimir to help identify the root cause. Sorry for that our wrong pattern makes LRA live range analysis confused. I will have a patch to fix it soon. Thanks both of you. :)