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/101617] New: a ? -1 : 1 -> (-(type)a) | 1
Date: Sun, 25 Jul 2021 05:47:46 +0000 [thread overview]
Message-ID: <bug-101617-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101617
Bug ID: 101617
Summary: a ? -1 : 1 -> (-(type)a) | 1
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: enhancement
Priority: P3
Component: tree-optimization
Assignee: pinskia at gcc dot gnu.org
Reporter: pinskia at gcc dot gnu.org
Target Milestone: ---
I noticed this while looking through a few bug reports but it deals with <=>
too.
Take:
int f(int i)
{
int t = i ? -1 : 0;
return t | 1;
}
int f1(int i)
{
return i ? -1 : 1;
}
------- CUT ------
These two should produce the same code generation.
Filing so I don't lose this while I am going through bug reports.
next reply other threads:[~2021-07-25 5:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-25 5:47 pinskia at gcc dot gnu.org [this message]
2021-07-25 5:47 ` [Bug tree-optimization/101617] " pinskia at gcc dot gnu.org
2021-07-25 19:25 ` pinskia at gcc dot gnu.org
2021-07-25 20:47 ` [Bug rtl-optimization/101617] " pinskia at gcc dot gnu.org
2021-07-25 22:03 ` pinskia at gcc dot gnu.org
2021-07-25 22:04 ` pinskia at gcc dot gnu.org
2021-07-25 22:35 ` pinskia at gcc dot gnu.org
2021-07-26 0:21 ` pinskia at gcc dot gnu.org
2021-07-26 0:28 ` pinskia at gcc dot gnu.org
2021-07-27 10:52 ` rguenth at gcc dot gnu.org
2022-05-30 20:28 ` cvs-commit at gcc dot gnu.org
2022-06-04 9:14 ` roger at nextmovesoftware dot com
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-101617-4@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).