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/108625] [11/12/13 Regression] forwprop introduces new UB Date: Wed, 01 Feb 2023 21:49:36 +0000 [thread overview] Message-ID: <bug-108625-4-XtKt7RMHa4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108625-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108625 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |wrong-code Ever confirmed|0 |1 Last reconfirmed| |2023-02-01 Target Milestone|--- |11.4 Summary|forwprop introduces new UB |[11/12/13 Regression] | |forwprop introduces new UB Status|UNCONFIRMED |NEW --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- GCC 12.1.0: Applying pattern match.pd:2763, gimple-match.cc:40998 Applying pattern match.pd:2532, gimple-match.cc:63517 Applying pattern match.pd:3647, gimple-match.cc:69622 gimple_simplified to _7 = t_2 - x_1(D); _5 = (unsigned char) _7; Introduced by r11-3207-g8f0d743c2dee6a . Confirmed.
next prev parent reply other threads:[~2023-02-01 21:49 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-01 9:10 [Bug tree-optimization/108625] New: " kristerw at gcc dot gnu.org 2023-02-01 21:49 ` pinskia at gcc dot gnu.org [this message] 2023-02-02 9:58 ` [Bug tree-optimization/108625] [11/12/13 Regression] " rguenth at gcc dot gnu.org 2023-02-02 12:13 ` cvs-commit at gcc dot gnu.org 2023-02-02 12:14 ` [Bug tree-optimization/108625] [11/12 " rguenth at gcc dot gnu.org 2023-03-15 9:47 ` cvs-commit at gcc dot gnu.org 2023-05-02 12:03 ` [Bug tree-optimization/108625] [11 " cvs-commit at gcc dot gnu.org 2023-05-02 12:06 ` 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-108625-4-XtKt7RMHa4@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).