public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jasonwucj at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/58295] [4.8/4.9 regression] Missed zero-extension elimination in the combiner
Date: Fri, 06 Sep 2013 09:54:00 -0000 [thread overview]
Message-ID: <bug-58295-4-sInPYAjJvE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58295-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58295
Chung-Ju Wu <jasonwucj at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jasonwucj at gmail dot com
--- Comment #2 from Chung-Ju Wu <jasonwucj at gmail dot com> ---
(In reply to Eric Botcazou from comment #1)
> combiner was indeed clever enough to do it. The QI subreg is clearly
> problematic for the ARM here (and probably most RISC architectures).
Yes. This problem also happens on our Andes nds32 architecture.
(The 'nds32' port is still awaiting for GWP approval before it
may be committed. But one can find its initial patch:
http://gcc.gnu.org/ml/gcc-patches/2013-08/msg01441.html)
As long as we revert r191928, which is the fix for pr54457, and
design the pattern in nds32.md to recognize the insn that
combiner created, the redundant insn 10 can be eliminated.
next prev parent reply other threads:[~2013-09-06 9:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 8:39 [Bug rtl-optimization/58295] New: The combination pass doesn't eliminates some extra zero extensions uranus at tinlans dot org
2013-09-02 22:02 ` [Bug rtl-optimization/58295] [4.8/4.9 regression] Missed zero-extension elimination in the combiner ebotcazou at gcc dot gnu.org
2013-09-06 9:54 ` jasonwucj at gmail dot com [this message]
2013-09-06 10:18 ` jakub at gcc dot gnu.org
2013-09-06 12:15 ` uranus at tinlans dot org
2013-09-06 13:18 ` ebotcazou at gcc dot gnu.org
2013-10-16 9:49 ` jakub at gcc dot gnu.org
2013-10-30 13:35 ` rguenth at gcc dot gnu.org
2013-10-30 18:02 ` ebotcazou at gcc dot gnu.org
2013-10-31 3:31 ` npickito at gmail dot com
2013-10-31 6:58 ` ebotcazou at gcc dot gnu.org
2013-10-31 7:14 ` npickito at gmail dot com
2013-10-31 8:02 ` ebotcazou at gcc dot gnu.org
2013-12-10 22:58 ` ebotcazou at gcc dot gnu.org
2013-12-10 22:59 ` ebotcazou at gcc dot gnu.org
2013-12-10 23:01 ` ebotcazou 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-58295-4-sInPYAjJvE@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).