public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/23115] [4.1 Regression] -ftree-vectorize generates wrong code
Date: Sun, 01 Jul 2007 13:40:00 -0000 [thread overview]
Message-ID: <20070701134035.15165.qmail@sourceware.org> (raw)
In-Reply-To: <bug-23115-1396@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from ubizjak at gmail dot com 2007-07-01 13:40 -------
(In reply to comment #9)
> PR tree-optimization/23115
> * tree-if-conv.c (find_phi_replacement_condition): Check domninated_by
> relation.
This fix is not enough to solve problems described in Comment #8. Actually, the
condition, introduced by attached patch:
+ || dominated_by_p (CDI_DOMINATORS, second_bb, first_bb))
doesn't even trigger anymore for the testcase in this PR, and at least gcc
4.3.0 passes mentioned testcase _only_ due to slightly different CFG. However,
the same problem (wrong handling of non perfect diamond) is the root cause of
PR 31966.
It is up to bugmaster to reopen this PR, as the fix is not effective.
--
ubizjak at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
OtherBugsDependingO| |31966
nThis| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23115
next prev parent reply other threads:[~2007-07-01 13:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-23115-1396@http.gcc.gnu.org/bugzilla/>
2005-10-22 21:56 ` pinskia at gcc dot gnu dot org
2005-10-31 4:23 ` mmitchel at gcc dot gnu dot org
2005-11-08 2:23 ` dpatel at apple dot com
2005-11-08 20:21 ` dpatel at gcc dot gnu dot org
2005-11-08 22:13 ` pinskia at gcc dot gnu dot org
2007-07-01 13:40 ` ubizjak at gmail dot com [this message]
2007-07-04 5:53 ` ubizjak at gmail dot com
2005-07-28 18:40 [Bug tree-optimization/23115] New: " p dot van-hoof at qub dot ac dot uk
2005-07-28 18:54 ` [Bug tree-optimization/23115] [4.1 Regression] " pinskia at gcc dot gnu dot org
2005-09-08 20:03 ` pinskia at gcc dot gnu dot org
2005-09-09 22:19 ` janis at gcc dot gnu dot org
2005-09-30 23:52 ` dpatel at apple dot com
2005-09-30 23:54 ` pinskia at gcc dot gnu dot 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=20070701134035.15165.qmail@sourceware.org \
--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).