public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/94427] 456.hmmer is 8-17% slower when compiled at -Ofast than with GCC 9
Date: Mon, 07 Aug 2023 09:44:44 +0000	[thread overview]
Message-ID: <bug-94427-4-SCFtoK0cE5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94427-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jan Hubicka from comment #4)
> It is the same loop - it was float only in my mind (since the function
> return float value :)
> 
> With loop splitting we no longer have the last iteration check, but we still
> have the underflow checks that are indeed likely predictable well and in
> unvectorized version may make sense to be not if converted.
> 
> So I guess in unvectorized loop the 100% predictable conditonal should be
> still a win but vectorization should likely outweight that?

I think so.

      parent reply	other threads:[~2023-08-07  9:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31 17:33 [Bug tree-optimization/94427] New: " jamborm at gcc dot gnu.org
2020-03-31 23:12 ` [Bug tree-optimization/94427] " jamborm at gcc dot gnu.org
2020-04-01  6:48 ` rguenth at gcc dot gnu.org
2023-08-07  9:19 ` hubicka at gcc dot gnu.org
2023-08-07  9:38 ` hubicka at gcc dot gnu.org
2023-08-07  9:44 ` rguenth at gcc dot gnu.org [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-94427-4-SCFtoK0cE5@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).