public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/57130] [4.8/4.9 Regression] Incorrect "and --> extract" conversion in combine
Date: Thu, 02 May 2013 09:07:00 -0000 [thread overview]
Message-ID: <bug-57130-4-TZaeeOUcu4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57130-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57130
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
AssignedTo|unassigned at gcc dot |jakub at gcc dot gnu.org
|gnu.org |
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-05-02 09:07:31 UTC ---
Created attachment 29994
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29994
gcc49-pr57130.patch
Untested fix, though not sure if it won't pessimize too much. The in_code ==
COMPARE handling simply look safe to me when recursing into a SUBREG.
Sometimes it could, e.g. for (subreg:SI (and:DI (reg:DI) (const_int
0x08000000))) with in_code == COMPARE, but we'd probably have to pass the
SUBREG mode around and special case it everywhere.
next prev parent reply other threads:[~2013-05-02 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 23:43 [Bug rtl-optimization/57130] New: " wmi at google dot com
2013-05-01 6:42 ` [Bug rtl-optimization/57130] [4.8/4.9 Regression] " jakub at gcc dot gnu.org
2013-05-02 6:58 ` jakub at gcc dot gnu.org
2013-05-02 9:07 ` jakub at gcc dot gnu.org [this message]
2013-05-02 9:23 ` jakub at gcc dot gnu.org
2013-05-02 10:49 ` jakub at gcc dot gnu.org
2013-05-03 13:57 ` jakub at gcc dot gnu.org
2021-07-24 22:03 ` pinskia at gcc dot gnu.org
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-57130-4-TZaeeOUcu4@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).