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/114203] [13/14 Regression] Miscompilation: A possible miscompilation in GCC 13 and 14 with option -Os Date: Sat, 02 Mar 2024 04:40:32 +0000 [thread overview] Message-ID: <bug-114203-4-qY3tuDkBfa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114203-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114203 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|c |tree-optimization Last reconfirmed| |2024-03-02 CC| |pinskia at gcc dot gnu.org Ever confirmed|0 |1 Target Milestone|--- |13.3 Keywords| |needs-bisection, wrong-code Summary|Miscompilation: A possible |[13/14 Regression] |miscompilation in GCC 13 |Miscompilation: A possible |and 14 with option -Os |miscompilation in GCC 13 | |and 14 with option -Os Status|UNCONFIRMED |NEW --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- final value replacement: c_7 = PHI <c_2(4)> with expr: b_3(D) != 0 ? 32 - __builtin_clz ((unsigned int) b_3(D)) : 24 24 is definitely wrong here. It should have been 0.
next prev parent reply other threads:[~2024-03-02 4:40 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-02 4:19 [Bug c/114203] New: " 141242068 at smail dot nju.edu.cn 2024-03-02 4:40 ` pinskia at gcc dot gnu.org [this message] 2024-03-04 9:36 ` [Bug tree-optimization/114203] [13/14 Regression] " rguenth at gcc dot gnu.org 2024-03-04 10:45 ` cvs-commit at gcc dot gnu.org 2024-03-04 10:46 ` [Bug tree-optimization/114203] [13 " rguenth at gcc dot gnu.org 2024-03-21 11:49 ` cvs-commit at gcc dot gnu.org 2024-03-21 11:51 ` rguenth 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-114203-4-qY3tuDkBfa@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: linkBe 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).