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 middle-end/110711] possible missed optimization for std::max with -march=znver2
Date: Wed, 19 Jul 2023 08:41:43 +0000	[thread overview]
Message-ID: <bug-110711-4-DmBiSCyWSn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110711-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110711

--- Comment #7 from Hongtao.liu <crazylht at gmail dot com> ---
git diff gcc12_171t.ifcvt gcc13.173.ifcvt

   <bb 5> [local count: 955630227]:
-  # i_22 = PHI <i_16(10), 1(19)>
+  # i_21 = PHI <i_16(10), 1(19)>
   # prephitmp_19 = PHI <prephitmp_24(10), _1(19)>
-  _2 = i_22 * 8;
+  _2 = i_21 * 8;
   _3 = a_10(D) + _2;
   _17 = MEM[(const double &)_3];
-  prephitmp_24 = MAX_EXPR <_17, prephitmp_19>;
-  i_16 = i_22 + 1;
+  _29 = MAX_EXPR <_17, prephitmp_19>;
+  prephitmp_24 = _29;
+  i_16 = i_21 + 1;
   if (n_els_7(D) > i_16)
     goto <bb 10>; [89.00%]
   else
     goto <bb 13>; [11.00%]

   <bb 13> [local count: 105119324]:
-  # prephitmp_13 = PHI <prephitmp_24(5), prephitmp_12(16)>
+  # prephitmp_15 = PHI <_29(5), prephitmp_27(16)>
   goto <bb 8>; [100.00%]

      parent reply	other threads:[~2023-07-19  8:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 10:11 [Bug middle-end/110711] New: " mrks2023 at proton dot me
2023-07-18 10:37 ` [Bug middle-end/110711] " crazylht at gmail dot com
2023-07-18 10:38 ` crazylht at gmail dot com
2023-07-18 12:03 ` rguenth at gcc dot gnu.org
2023-07-18 12:03 ` rguenth at gcc dot gnu.org
2023-07-19  6:57 ` crazylht at gmail dot com
2023-07-19  8:34 ` crazylht at gmail dot com
2023-07-19  8:37 ` crazylht at gmail dot com
2023-07-19  8:41 ` crazylht at gmail dot com [this message]

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-110711-4-DmBiSCyWSn@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).