public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sergos.gnu at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/54717] [4.8 Regression] Runtime regression: polyhedron test "rnflow" degraded
Date: Wed, 26 Sep 2012 20:07:00 -0000 [thread overview]
Message-ID: <bug-54717-4-OLQssKZxyC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54717-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54717
--- Comment #5 from Sergey Ostanevich <sergos.gnu at gmail dot com> 2012-09-26 20:07:26 UTC ---
for 093t.pre I see the following missing in cptrf2 function, first is good,
second is degraded:
***************
*** 8947,8966 ****
goto <bb 35>;
<bb 93>:
- pretmp_325 = (integer(kind=8)) ival2_80;
- pretmp_326 = pretmp_325 + -1;
- pretmp_327 = *xxtrt_25(D)[pretmp_326];
<bb 27>:
# ival2_136 = PHI <ival2_62(93), ival2_144(97)>
# ival2_140 = PHI <ival2_80(93), ival2_146(97)>
- # prephitmp_328 = PHI <pretmp_327(93), prephitmp_290(97)>
_137 = (integer(kind=8)) ival2_136;
_138 = _137 + -1;
_139 = *xxtrt_25(D)[_138];
_141 = (integer(kind=8)) ival2_140;
_142 = _141 + -1;
! _143 = prephitmp_328;
if (_139 < _143)
goto <bb 28>;
else
--- 8838,8853 ----
goto <bb 35>;
<bb 93>:
<bb 27>:
# ival2_136 = PHI <ival2_62(93), ival2_144(97)>
# ival2_140 = PHI <ival2_80(93), ival2_146(97)>
_137 = (integer(kind=8)) ival2_136;
_138 = _137 + -1;
_139 = *xxtrt_25(D)[_138];
_141 = (integer(kind=8)) ival2_140;
_142 = _141 + -1;
! _143 = *xxtrt_25(D)[_142];
if (_139 < _143)
goto <bb 28>;
else
***************
but more surprising to me is that first diff is in 020t.inline_param1
***************
*** 16790,16794 ****
calls:
dtrti2/26 function not considered for inlining
! loop depth: 0 freq:1000 size: 9 time: 18 callee size:82 stack:28
dtrsm/21 function not considered for inlining
loop depth: 0 freq:1000 size:16 time: 25 callee size:324 stack: 4
--- 16790,16794 ----
calls:
dtrti2/26 function not considered for inlining
! loop depth: 0 freq:1000 size: 9 time: 18 callee size:81 stack:28
dtrsm/21 function not considered for inlining
loop depth: 0 freq:1000 size:16 time: 25 callee size:324 stack: 4
***************
next prev parent reply other threads:[~2012-09-26 20:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 12:54 [Bug tree-optimization/54717] New: " sergos.gnu at gmail dot com
2012-09-26 13:17 ` [Bug tree-optimization/54717] " ubizjak at gmail dot com
2012-09-26 14:17 ` [Bug tree-optimization/54717] [4.8 Regression] " rguenth at gcc dot gnu.org
2012-09-26 15:12 ` sergos.gnu at gmail dot com
2012-09-26 15:41 ` dominiq at lps dot ens.fr
2012-09-26 20:07 ` sergos.gnu at gmail dot com [this message]
2012-09-27 9:28 ` rguenth at gcc dot gnu.org
2012-09-27 10:43 ` rguenth at gcc dot gnu.org
2012-10-02 20:24 ` dominiq at lps dot ens.fr
2012-10-08 8:55 ` sergos.gnu at gmail dot com
2012-11-13 18:40 ` ubizjak at gmail dot com
2012-11-13 18:54 ` dominiq at lps dot ens.fr
2012-11-14 18:56 ` sergos.gnu at gmail dot com
2012-11-14 19:42 ` Jan Hubicka
2012-11-14 19:43 ` hubicka at ucw dot cz
2012-11-14 20:11 ` hubicka at gcc dot gnu.org
2012-11-15 10:28 ` hubicka at gcc dot gnu.org
2012-11-15 10:52 ` hubicka at gcc dot gnu.org
2012-11-15 15:07 ` dominiq at lps dot ens.fr
2012-11-16 10:37 ` hubicka at gcc dot gnu.org
2012-12-06 16:51 ` rguenth 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-54717-4-OLQssKZxyC@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).