public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Alex.Velenko at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/64916] New: ira.c update_equiv_regs patch causes gcc/testsuite/gcc.target/arm/pr43920-2.c regression
Date: Tue, 03 Feb 2015 12:34:00 -0000 [thread overview]
Message-ID: <bug-64916-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64916
Bug ID: 64916
Summary: ira.c update_equiv_regs patch causes
gcc/testsuite/gcc.target/arm/pr43920-2.c regression
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: Alex.Velenko at arm dot com
CC: amker.cheng at gmail dot com, fei.yang0953 at gmail dot com,
law at redhat dot com, marcus.shawcroft at arm dot com
Build: arm-none-eabi
Created attachment 34650
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34650&action=edit
Tar with patched and non-patched rtl dump file tars
In pr43920-2.c code block for "return -1;" c statement is not getting reused
after
ira.c update_equiv_regs patch. I believe svn it's number is r216169.
Reason - patch removes "(expr_list:REG_EQUAL (const_int -1
[0xffffffffffffffff])" note in ira pass, which prevents jump2 optimization.
This information still needs to be passed to jump2 pass.
See rtl dump attachments below.
next reply other threads:[~2015-02-03 12:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 12:34 Alex.Velenko at arm dot com [this message]
2015-02-03 13:38 ` [Bug rtl-optimization/64916] [5.0 regression] " ramana at gcc dot gnu.org
2015-02-04 2:52 ` amker at gcc dot gnu.org
2015-02-09 0:06 ` [Bug rtl-optimization/64916] [5 " pinskia at gcc dot gnu.org
2015-02-09 23:35 ` [Bug rtl-optimization/64916] " law at redhat dot com
2015-03-12 16:55 ` ramana at gcc dot gnu.org
2015-04-21 5:23 ` law at gcc dot gnu.org
2015-04-21 5:41 ` law at redhat dot com
2015-04-22 8:51 ` Alex.Velenko at arm dot com
2015-04-22 13:28 ` Alex.Velenko at arm dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-64916-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).