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/112402] New: [11/12/13/14 Regression] Path splitting causes if-conversion miss
Date: Mon, 06 Nov 2023 06:53:25 +0000 [thread overview]
Message-ID: <bug-112402-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112402
Bug ID: 112402
Summary: [11/12/13/14 Regression] Path splitting causes
if-conversion miss
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: pinskia at gcc dot gnu.org
Blocks: 94274
Target Milestone: ---
Similar to PR 68541 except instead of having a diamond, we just have a
triangle.
Testcase:
```
int
foo(signed char *p, int n)
{
int s = 0;
int i;
for (i = 0; i < n; i++) {
int t;
if (p[i] >= 0)
t=1;
else
t=-1;
s+=t;
}
return s;
}
```
I noticed this while working on fixing PR 94274.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94274
[Bug 94274] fold phi whose incoming args are defined from binary operations
next reply other threads:[~2023-11-06 6:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 6:53 pinskia at gcc dot gnu.org [this message]
2023-11-06 6:53 ` [Bug tree-optimization/112402] " pinskia at gcc dot gnu.org
2023-11-06 8:37 ` rguenth at gcc dot gnu.org
2023-11-07 3:27 ` pinskia at gcc dot gnu.org
2023-11-09 20:25 ` pinskia at gcc dot gnu.org
2024-03-07 21:03 ` law 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-112402-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).