public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <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: Thu, 21 Dec 2023 20:06:56 +0000 [thread overview] Message-ID: <bug-112758-4-mnrGa3jXH0@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 #16 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Here is what I'd propose, but I can't really test it on any WORD_REGISTER_OPERATIONS target. 2023-12-21 Jakub Jelinek <jakub@redhat.com> PR rtl-optimization/112758 * combine.cc (make_compopund_operation_int): Optimize AND of a SUBREG based on nonzero_bits of SUBREG_REG and constant mask on WORD_REGISTER_OPERATIONS targets only if it is a zero extending MEM load. * gcc.c-torture/execute/pr112758.c: New test. --- gcc/combine.cc.jj 2023-12-11 23:52:03.528513943 +0100 +++ gcc/combine.cc 2023-12-21 20:25:45.461737423 +0100 @@ -8227,12 +8227,20 @@ make_compound_operation_int (scalar_int_ int sub_width; if ((REG_P (sub) || MEM_P (sub)) && GET_MODE_PRECISION (sub_mode).is_constant (&sub_width) - && sub_width < mode_width) + && sub_width < mode_width + && (!WORD_REGISTER_OPERATIONS + || sub_width >= BITS_PER_WORD + /* On WORD_REGISTER_OPERATIONS targets the bits + beyond sub_mode aren't considered undefined, + so optimize only if it is a MEM load when MEM loads + zero extend, because then the upper bits are all zero. */ + || (MEM_P (sub) + && load_extend_op (sub_mode) == ZERO_EXTEND))) { unsigned HOST_WIDE_INT mode_mask = GET_MODE_MASK (sub_mode); unsigned HOST_WIDE_INT mask; - /* original AND constant with all the known zero bits set */ + /* Original AND constant with all the known zero bits set. */ mask = UINTVAL (XEXP (x, 1)) | (~nonzero_bits (sub, sub_mode)); if ((mask & mode_mask) == mode_mask) { --- gcc/testsuite/gcc.c-torture/execute/pr112758.c.jj 2023-12-21 21:01:43.780755959 +0100 +++ gcc/testsuite/gcc.c-torture/execute/pr112758.c 2023-12-21 21:01:30.521940358 +0100 @@ -0,0 +1,15 @@ +/* PR rtl-optimization/112758 */ + +int a = -__INT_MAX__ - 1; + +int +main () +{ + if (-__INT_MAX__ - 1U == 0x80000000ULL) + { + unsigned long long b = 0xffff00ffffffffffULL; + if ((b & a) != 0xffff00ff80000000ULL) + __builtin_abort (); + } + return 0; +}
next prev parent reply other threads:[~2023-12-21 20:06 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 2023-12-21 20:04 ` gkm at rivosinc dot com 2023-12-21 20:06 ` jakub at gcc dot gnu.org [this message] 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-mnrGa3jXH0@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).