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/110165] New: [13/14 Regression] wrong code with signed 1 bit integers sometimes since r13-4459-g6508d5e5a1a8 Date: Wed, 07 Jun 2023 23:27:40 +0000 [thread overview] Message-ID: <bug-110165-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110165 Bug ID: 110165 Summary: [13/14 Regression] wrong code with signed 1 bit integers sometimes since r13-4459-g6508d5e5a1a8 Product: gcc Version: 13.1.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P3 Component: tree-optimization Assignee: pinskia at gcc dot gnu.org Reporter: pinskia at gcc dot gnu.org Target Milestone: --- Full testcase: ```` struct s { int t : 1; }; [[gnu::noipa]] int f(struct s t, int a, int b) { int bd = t.t; if (bd) a|=b; return a; } int main(void) { struct s t; for(int i = 0;i <= 1; i++) { int a = 0x10; int b = 0x0f; int c = a | b; int r = f((struct s){i}, a, b); int exp = i == 1 ? a | b : a; if (exp != r) __builtin_abort(); } } ``` Found while improving these match patterns.
next reply other threads:[~2023-06-07 23:27 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-07 23:27 pinskia at gcc dot gnu.org [this message] 2023-06-07 23:28 ` [Bug tree-optimization/110165] " pinskia at gcc dot gnu.org 2023-06-08 1:24 ` pinskia at gcc dot gnu.org 2023-06-08 1:52 ` pinskia at gcc dot gnu.org 2023-06-08 10:17 ` jakub at gcc dot gnu.org 2023-06-08 13:39 ` pinskia at gcc dot gnu.org 2023-06-08 20:49 ` pinskia at gcc dot gnu.org 2023-06-09 6:53 ` rguenth at gcc dot gnu.org 2023-06-09 14:15 ` cvs-commit at gcc dot gnu.org 2023-06-09 14:18 ` [Bug tree-optimization/110165] [13 " pinskia at gcc dot gnu.org 2023-06-09 22:13 ` cvs-commit at gcc dot gnu.org 2023-06-09 22:15 ` pinskia 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-110165-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: 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).