public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/19786] [4.0 Regression] Aliasing optimisation bug
Date: Wed, 16 Feb 2005 23:17:00 -0000 [thread overview]
Message-ID: <20050216191413.18898.qmail@sourceware.org> (raw)
In-Reply-To: <20050206101741.19786.sylvain.pion@sophia.inria.fr>
------- Additional Comments From jakub at gcc dot gnu dot org 2005-02-16 19:14 -------
I'm still looking into it.
While with -fno-strict-aliasing the important part of the dump is:
# BLOCK 20
# PRED: 33 [100.0%] (fallthru) 30 [100.0%] (fallthru)
# TMT.382D.16594_470 = PHI <TMT.382D.16594_1015(33), TMT.382D.16594_1010(30)>;
<L110>:;
D.16463_352 = &thisD.16043_125->D.11755._M_implD.11232._M_finishD.11380;
__iD.16464_353 = D.16463_352;
# VUSE <TMT.382D.16594_470>;
SR.538D.16754_354 = *__iD.16464_353;
D.16471_365 = SR.538D.16754_354 - 4B;
# VUSE <TMT.382D.16594_470>;
D.16033_377 = *D.16471_365;
...
<L117>:;
# VUSE <TMT.382D.16594_470>;
D.16404_339 = thisD.16043_125->D.11755._M_implD.11232._M_finishD.11380;
D.16405_340 = D.16404_339 - 4B;
# TMT.382D.16594_1015 = V_MAY_DEF <TMT.382D.16594_470>;
thisD.16043_125->D.11755._M_implD.11232._M_finishD.11380 = D.16405_340;
...
loop to 110, so TMT.382D.16594_470 = PHI <TMT.382D.16594_1015(33),
TMT.382D.16594_1010(30)> is in the loop, with -fstrict-aliasing we have:
# BLOCK 19
# PRED: 17 [100.0%] (fallthru,exec) 28 [100.0%] (fallthru)
# TMT.412D.16624_469 = PHI <TMT.412D.16624_1050(17), TMT.412D.16624_1037(28)>;
# TMT.411D.16623_22 = PHI <TMT.411D.16623_392(17), TMT.411D.16623_244(28)>;
# D.16251_470 = PHI <D.16251_380(17), D.16251_242(28)>;
# D.16077_471 = PHI <D.16077_384(17), D.16077_243(28)>;
<L97>:;
...
# BLOCK 20
# PRED: 33 [100.0%] (fallthru) 30 [100.0%] (fallthru)
# TMT.411D.16623_2 = PHI <TMT.411D.16623_260(33), TMT.411D.16623_22(30)>;
<L110>:;
D.16491_352 = &thisD.16071_125->D.11755._M_implD.11232._M_finishD.11380;
__iD.16492_353 = D.16491_352;
# VUSE <TMT.412D.16624_469>;
SR.574D.16790_354 = *__iD.16492_353;
D.16499_365 = SR.574D.16790_354 - 4B;
# VUSE <D.16077_280>;
# VUSE <D.16251_279>;
D.16061_377 = *D.16499_365;
...
but TMT.412D.16624_469 = PHI <TMT.412D.16624_1050(17), TMT.412D.16624_1037(28)>
is outside of the loop (loop starts at L110).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19786
next prev parent reply other threads:[~2005-02-16 19:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 10:17 [Bug tree-optimization/19786] New: " sylvain.pion@sophia.inria.fr
2005-02-06 10:20 ` [Bug tree-optimization/19786] " sylvain.pion@sophia.inria.fr
2005-02-06 15:19 ` pinskia@gcc.gnu.org
2005-02-06 15:29 ` [Bug rtl-optimization/19786] [4.0 Regression] " pinskia@gcc.gnu.org
2005-02-07 3:24 ` pinskia at gcc dot gnu dot org
2005-02-07 3:25 ` pinskia at gcc dot gnu dot org
2005-02-07 3:39 ` pinskia at gcc dot gnu dot org
2005-02-07 3:42 ` pinskia at gcc dot gnu dot org
2005-02-16 19:46 ` jakub at gcc dot gnu dot org
2005-02-16 20:04 ` jakub at gcc dot gnu dot org
2005-02-16 22:00 ` [Bug tree-optimization/19786] " pinskia at gcc dot gnu dot org
2005-02-16 23:17 ` jakub at gcc dot gnu dot org [this message]
2005-02-17 3:30 ` jakub at gcc dot gnu dot org
2005-02-18 22:00 ` aoliva at gcc dot gnu dot org
2005-02-19 1:14 ` sylvain dot pion at sophia dot inria dot fr
2005-02-19 11:53 ` aoliva at gcc dot gnu dot org
2005-02-21 21:47 ` pinskia at gcc dot gnu dot org
2005-02-21 23:19 ` aoliva at redhat dot com
2005-02-21 23:23 ` dnovillo at redhat dot com
2005-02-22 11:32 ` cvs-commit at gcc dot gnu dot org
2005-02-22 12:02 ` 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=20050216191413.18898.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).