public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109424] ~((x > y) ? x : y) produces two not instructions
Date: Wed, 05 Apr 2023 19:47:49 +0000 [thread overview]
Message-ID: <bug-109424-4-paUtFOs82N@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109424-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109424
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|~ |~((x > y) ? x : y) produces
| |two not instructions
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> You would assume GCC produce the same code for both, but nope, the first f is worse.
Sorry f1 is worse.
next prev parent reply other threads:[~2023-04-05 19:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 19:47 [Bug tree-optimization/109424] New: ~ pinskia at gcc dot gnu.org
2023-04-05 19:47 ` pinskia at gcc dot gnu.org [this message]
2023-04-05 19:48 ` [Bug tree-optimization/109424] ~((x > y) ? x : y) produces two not instructions pinskia at gcc dot gnu.org
2023-04-07 16:29 ` roger at nextmovesoftware dot com
2023-04-16 18:32 ` pinskia at gcc dot gnu.org
2023-05-08 7:38 ` cvs-commit at gcc dot gnu.org
2023-05-08 7:39 ` pinskia at gcc dot gnu.org
2023-05-08 7:41 ` pinskia at gcc dot gnu.org
2023-05-16 3:50 ` cvs-commit 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-109424-4-paUtFOs82N@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).