public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <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: Thu, 31 Oct 2013 06:58:00 -0000 [thread overview]
Message-ID: <bug-58295-4-m3SRdF9zhR@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
--- Comment #11 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> So why don't reject it at
> TARGET_LEGITIMATE_COMBINED_INSN/ix86_legitimate_combined_insn
> instead of limit at combine phase if it's only benefit for x86 ?
The question sounds self-contradictory... Anyway, rather than inventing a new
hook for each problem, let's try to formulate it in terms of existing hooks.
next prev parent reply other threads:[~2013-10-31 6:58 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
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 [this message]
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-m3SRdF9zhR@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).