From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21478 invoked by alias); 29 Oct 2014 09:25:01 -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 21430 invoked by uid 48); 29 Oct 2014 09:24:55 -0000 From: "ramana at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/63210] ira does not select the best register compared with gcc 4.8 for ARM THUMB1 Date: Wed, 29 Oct 2014 09:28:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ramana at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution target_milestone 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-10/txt/msg02226.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63210 Ramana Radhakrishnan changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Target Milestone|--- |5.0 --- Comment #5 from Ramana Radhakrishnan --- (In reply to Zhenqiang Chen from comment #4) > (In reply to Ramana Radhakrishnan from comment #3) > > Fixed is it? And does it fail in GCC 4.9 ? > > Fixed on trunk. Same fail in GCC 4.9. > > It is a performance issue. Do you think it is OK for 4.9? If it is a 4.9 regression you should be marking it as so in the bug report- change the title to [4.9 regression] and fill up the "Known to Fail" fields. I cannot possibly comment if it is suitable for 4.9 branch or not. I'm marking this as fixed for 5.0 - if you get this backported please remember to change the target milestone to the appropriate 4.9 milestone.