public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amker at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/62151] [5 Regression] wrong code at -O2 and -O3 on x86_64-linux-gnu
Date: Wed, 20 Aug 2014 02:32:00 -0000 [thread overview]
Message-ID: <bug-62151-4-Obpksjk3zQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62151-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62151
--- Comment #9 from amker at gcc dot gnu.org ---
(In reply to Eric Botcazou from comment #8)
> > I will try to test a patch, meanwhile, I am wondering if any combine expert
> > has something to share.
>
> distribute_notes is certainly an endless source of bugs.
One patch is sent at https://gcc.gnu.org/ml/gcc-patches/2014-08/msg01718.html
It's a scratch patch for discussion's purpose. Though I think it's right to
find distribution place for REG_DEAD note starting from i2 if it kills the
register, I am not sure if it's fixing the issue in a case by case manner. So
it's highly appreciated if any expert in this area can share some opinions, or
review the patch?
>
> > BTW, combine pass seems to be another ad-hoc implementation like reload, I saw
> > several "Don't know" in comments during this investigation!
>
> You would need to define what an "ad-hoc implementation" is exactly. See
> the top of the file for the origin of the pass.
Err, I may used the wrong word. These are just frustrating words after seeing
several "Don't know" comments in the code. Please ignore them.
Thanks.
next prev parent reply other threads:[~2014-08-20 2:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 6:14 [Bug tree-optimization/62151] New: " su at cs dot ucdavis.edu
2014-08-15 7:33 ` [Bug tree-optimization/62151] [5 Regression] " mpolacek at gcc dot gnu.org
2014-08-15 7:34 ` mpolacek at gcc dot gnu.org
2014-08-15 7:42 ` [Bug rtl-optimization/62151] " mpolacek at gcc dot gnu.org
2014-08-15 7:55 ` jakub at gcc dot gnu.org
2014-08-15 8:04 ` amker at gcc dot gnu.org
2014-08-15 9:53 ` rguenth at gcc dot gnu.org
2014-08-15 9:53 ` rguenth at gcc dot gnu.org
2014-08-15 15:39 ` amker at gcc dot gnu.org
2014-08-16 12:11 ` amker at gcc dot gnu.org
2014-08-19 18:55 ` ebotcazou at gcc dot gnu.org
2014-08-20 2:32 ` amker at gcc dot gnu.org [this message]
2014-10-02 2:18 ` segher at gcc dot gnu.org
2014-10-02 2:30 ` segher at gcc dot gnu.org
2014-12-09 8:48 ` amker.cheng at gmail dot com
2014-12-09 9:27 ` amker.cheng at gmail dot com
2014-12-10 8:14 ` amker at gcc dot gnu.org
2014-12-11 3:10 ` amker.cheng at gmail dot com
2014-12-11 8:52 ` amker at gcc dot gnu.org
2014-12-22 10:25 ` amker at gcc dot gnu.org
2014-12-22 10:29 ` amker 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-62151-4-Obpksjk3zQ@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).