public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/105216] [12 regression] 8% regression for m-queens compared to gcc11 O2 on CLX.
Date: Mon, 11 Apr 2022 10:14:41 +0000 [thread overview]
Message-ID: <bug-105216-4-t0Lyi444O7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105216-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105216
--- Comment #6 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Hongtao.liu from comment #5)
> My bisect shows it's caused by
> r12-3876-g4a960d548b7d7d942f316c5295f6d849b74214f5
pre dump before vs after
- goto <bb 21>; [11.00%]
-
- <bb 12> [local count: 105119324]:
- pretmp_379 = cols[d_243]; ---- miss optimization here.
-
- <bb 13> [local count: 955630226]:
- # level4_cnt_250 = PHI <level4_cnt_236(20), level4_cnt_242(12)>
- # d_252 = PHI <d_98(20), d_243(12)>
- # posib_254 = PHI <posib_102(20), posib_244(12)>
- # diagl_shifted_255 = PHI <diagl_shifted_103(20), diagl_shifted_184(12)>
- # diagr_shifted_256 = PHI <diagr_shifted_104(20), diagr_shifted_185(12)>
- # l_rest_257 = PHI <l_rest_115(20), prephitmp_366(12)>
- # prephitmp_380 = PHI <prephitmp_378(20), pretmp_379(12)>
+ goto <bb 19>; [11.00%]
+
+ <bb 12> [local count: 955630226]:
+ # level4_cnt_250 = PHI <level4_cnt_205(18), level4_cnt_242(11)>
+ # d_252 = PHI <d_47(18), d_243(11)>
+ # posib_254 = PHI <posib_27(18), posib_244(11)>
+ # diagl_shifted_255 = PHI <diagl_shifted_25(18), diagl_shifted_184(11)>
+ # diagr_shifted_256 = PHI <diagr_shifted_24(18), diagr_shifted_185(11)>
+ # l_rest_257 = PHI <l_rest_13(18), prephitmp_313(11)>
_30 = ~posib_254;
_31 = posib_254 + 1;
bit_189 = _30 & _31;
@@ -1030,15 +1037,16 @@ uint64_t nqueens (uint_fast8_t n)
new_diagl_191 = _32 | diagl_shifted_255;
_33 = bit_189 >> 1;
new_diagr_192 = _33 | diagr_shifted_256;
- bit_193 = bit_189 | prephitmp_380;
+ _34 = cols[d_252];
+ bit_193 = _34 | bit_189;
next prev parent reply other threads:[~2022-04-11 10:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 7:57 [Bug tree-optimization/105216] New: [12 regression] 8% regression for m-queens compared to gcc11 O2 crazylht at gmail dot com
2022-04-11 8:12 ` [Bug tree-optimization/105216] " pinskia at gcc dot gnu.org
2022-04-11 8:18 ` rguenth at gcc dot gnu.org
2022-04-11 8:35 ` crazylht at gmail dot com
2022-04-11 8:38 ` rguenth at gcc dot gnu.org
2022-04-11 10:08 ` [Bug tree-optimization/105216] [12 regression] 8% regression for m-queens compared to gcc11 O2 on CLX crazylht at gmail dot com
2022-04-11 10:14 ` crazylht at gmail dot com [this message]
2022-04-11 10:24 ` rguenther at suse dot de
2022-04-11 12:07 ` crazylht at gmail dot com
2022-04-11 12:13 ` crazylht at gmail dot com
2022-04-12 3:11 ` crazylht at gmail dot com
2022-04-12 6:15 ` crazylht at gmail dot com
2022-04-26 15:08 ` [Bug tree-optimization/105216] [12 regression] 8% regression for m-queens compared to gcc11 O2 on CLX. since r12-3876-g4a960d548b7d7d94 marxin at gcc dot gnu.org
2022-05-06 8:33 ` [Bug tree-optimization/105216] [12/13 " jakub at gcc dot gnu.org
2022-07-26 12:34 ` rguenth at gcc dot gnu.org
2022-12-31 4:30 ` pinskia at gcc dot gnu.org
2023-01-03 1:01 ` crazylht at gmail dot com
2023-05-08 12:24 ` [Bug tree-optimization/105216] [12/13/14 " 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-105216-4-t0Lyi444O7@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).