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/110640] [13 Regression] Wrong code at -O2/3 on x86_64-linux-gnu since GCC-13 since r12-1653-gcb448ade74d
Date: Thu, 14 Dec 2023 07:37:13 +0000 [thread overview]
Message-ID: <bug-110640-4-IMCuGWYuqA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110640-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110640
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work| |14.0
Summary|[13/14 Regression] Wrong |[13 Regression] Wrong code
|code at -O2/3 on |at -O2/3 on
|x86_64-linux-gnu since |x86_64-linux-gnu since
|GCC-13 since |GCC-13 since
|r12-1653-gcb448ade74d |r12-1653-gcb448ade74d
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Depends on| |111445
Status|NEW |ASSIGNED
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #6)
> This doesn't reproduce on the trunk since
> r14-4790-g9692309ed6b625f0fb358c0e230404b5603f69a6 anymore. Was that a fix
> for this or just made it latent?
It does look similar enough:
<bb 7> [local count: 118111600]:
k_11 = k_38 + 1;
- _13 = (unsigned char) j_12(D);
- _14 = _13 + 1;
- _15 = (int) _14;
+ _13 = _26;
+ _14 = _28;
+ _15 = _29;
_16 = (int) k_11;
- _17 = _15 + _16;
+ _17 = _29 + 1;
I'll add this testcase as well.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111445
[Bug 111445] [12 Regression] Wrong code at -Os on x86_64-linux-gnu since
r12-1077-g57bf3751511
next prev parent reply other threads:[~2023-12-14 7:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 12:45 [Bug c/110640] New: Wrong code at -O2/3 on x86_64-linux-gnu since GCC-13 shaohua.li at inf dot ethz.ch
2023-07-12 13:55 ` [Bug c/110640] [13/14 Regression] " rguenth at gcc dot gnu.org
2023-07-12 13:56 ` [Bug tree-optimization/110640] " rguenth at gcc dot gnu.org
2023-07-12 16:19 ` pinskia at gcc dot gnu.org
2023-07-13 8:51 ` rguenth at gcc dot gnu.org
2023-07-27 9:27 ` rguenth at gcc dot gnu.org
2023-07-30 14:49 ` shaohua.li at inf dot ethz.ch
2023-07-31 7:15 ` rguenth at gcc dot gnu.org
2023-12-13 17:03 ` jakub at gcc dot gnu.org
2023-12-14 7:37 ` rguenth at gcc dot gnu.org [this message]
2023-12-14 7:39 ` [Bug tree-optimization/110640] [13 Regression] Wrong code at -O2/3 on x86_64-linux-gnu since GCC-13 since r12-1653-gcb448ade74d rguenth at gcc dot gnu.org
2023-12-14 7:41 ` 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-110640-4-IMCuGWYuqA@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).