public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gkm at rivosinc dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/112758] [13/14 Regression] Inconsistent Bitwise AND Operation Result between int and long long int Date: Sat, 16 Dec 2023 18:43:35 +0000 [thread overview] Message-ID: <bug-112758-4-B3x6F4NMJ8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112758-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112758 --- Comment #14 from Greg McGary <gkm at rivosinc dot com> --- I bisected to here for the commit that broke the non-Zbs case: https://github.com/gcc-mirror/gcc/commit/2e886eef7f2b5aadb00171af868f0895b647c3a4 ... and here for Zbs case: https://github.com/gcc-mirror/gcc/commit/4e1e0d79ecbe8727cb69d4cd97b20c71caaefafc Note that the Zbs break happens with the commit that introduces Zbs handling, i.e., it never worked with Zbs from the beginning. In the non-Zbs case, it was the introduction of the insn_and_split pattern for single-insn materialization of negative constants that allows the combiner to create the problematic insn.
next prev parent reply other threads:[~2023-12-16 18:43 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-29 6:05 [Bug c/112758] New: Inconsistent Bitwise AND Operation Result between int and long long int on Different Optimization Levels in GCC Trunk guminb at ajou dot ac.kr 2023-11-29 18:18 ` [Bug rtl-optimization/112758] [13/14 Regression] Inconsistent Bitwise AND Operation Result between int and long long int pinskia at gcc dot gnu.org 2023-12-08 2:57 ` guminb at ajou dot ac.kr 2023-12-08 17:01 ` jakub at gcc dot gnu.org 2023-12-08 17:37 ` segher at gcc dot gnu.org 2023-12-08 19:33 ` jakub at gcc dot gnu.org 2023-12-08 19:36 ` jakub at gcc dot gnu.org 2023-12-09 8:51 ` ebotcazou at gcc dot gnu.org 2023-12-09 9:11 ` jakub at gcc dot gnu.org 2023-12-09 11:00 ` ebotcazou at gcc dot gnu.org 2023-12-09 19:25 ` segher at gcc dot gnu.org 2023-12-09 22:06 ` ebotcazou at gcc dot gnu.org 2023-12-10 12:16 ` segher at gcc dot gnu.org 2023-12-13 22:06 ` pinskia at gcc dot gnu.org 2023-12-16 18:43 ` gkm at rivosinc dot com [this message] 2023-12-21 20:04 ` gkm at rivosinc dot com 2023-12-21 20:06 ` jakub at gcc dot gnu.org 2023-12-22 11:30 ` cvs-commit at gcc dot gnu.org 2024-03-02 0:37 ` cvs-commit at gcc dot gnu.org 2024-03-04 1:09 ` law at gcc dot gnu.org 2024-03-04 12:07 ` [Bug rtl-optimization/112758] [13 " jakub 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-112758-4-B3x6F4NMJ8@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).