public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/103194] [12 Regression] ice in optimize_atomic_bit_test_and with __sync_fetch_and_and Date: Thu, 11 Nov 2021 18:56:15 +0000 [thread overview] Message-ID: <bug-103194-4-5V9bBLR5JZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103194-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103194 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2021-11-11 Ever confirmed|0 |1 --- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> --- The narrowing cast isn't handled: [hjl@gnu-cfl-2 pr102566]$ cat x3.c #include <stdatomic.h> int foo (_Atomic long long int *v) { return atomic_fetch_or_explicit (v, 1, memory_order_relaxed) & 1; } [hjl@gnu-cfl-2 pr102566]$ make x3.s /export/build/gnu/tools-build/gcc-gitlab-debug/build-x86_64-linux/gcc/xgcc -B/export/build/gnu/tools-build/gcc-gitlab-debug/build-x86_64-linux/gcc/ -O2 -S x3.c [hjl@gnu-cfl-2 pr102566]$ cat x3.s .file "x3.c" .text .p2align 4 .globl foo .type foo, @function foo: .LFB0: .cfi_startproc movq (%rdi), %rax .L2: movq %rax, %rcx movq %rax, %rdx orq $1, %rcx lock cmpxchgq %rcx, (%rdi) jne .L2 movl %edx, %eax andl $1, %eax ret .cfi_endproc .LFE0: .size foo, .-foo .ident "GCC: (GNU) 12.0.0 20211111 (experimental)" .section .note.GNU-stack,"",@progbits [hjl@gnu-cfl-2 pr102566]$
next prev parent reply other threads:[~2021-11-11 18:56 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-11 16:48 [Bug c/103194] New: ice in optimize_atomic_bit_test_and, at tree-ssa-ccp.c:3626 dcb314 at hotmail dot com 2021-11-11 16:50 ` [Bug c/103194] " dcb314 at hotmail dot com 2021-11-11 17:20 ` [Bug tree-optimization/103194] [12 Regression] ice in optimize_atomic_bit_test_and with __sync_fetch_and_and pinskia at gcc dot gnu.org 2021-11-11 18:56 ` hjl.tools at gmail dot com [this message] 2021-11-12 7:35 ` rguenth at gcc dot gnu.org 2021-11-12 9:29 ` [Bug tree-optimization/103194] [12 Regression] ice in optimize_atomic_bit_test_and with __sync_fetch_and_and since r12-5102-gfb161782545224f5 marxin at gcc dot gnu.org 2021-11-12 13:43 ` hjl.tools at gmail dot com 2021-11-13 15:04 ` hjl.tools at gmail dot com 2021-11-13 15:11 ` hjl.tools at gmail dot com 2021-11-15 1:23 ` crazylht at gmail dot com 2021-11-15 2:47 ` crazylht at gmail dot com 2021-11-15 8:32 ` crazylht at gmail dot com 2021-11-15 9:06 ` crazylht at gmail dot com 2021-11-15 9:12 ` pinskia at gcc dot gnu.org 2021-11-16 1:30 ` crazylht at gmail dot com 2021-11-16 1:49 ` hjl.tools at gmail dot com 2021-11-16 1:51 ` hjl.tools at gmail dot com 2021-11-16 2:24 ` crazylht at gmail dot com 2021-11-16 2:39 ` hjl.tools at gmail dot com 2021-11-16 3:26 ` hjl.tools at gmail dot com 2021-11-16 6:19 ` crazylht at gmail dot com 2021-11-16 6:45 ` crazylht at gmail dot com 2021-11-24 1:01 ` cvs-commit at gcc dot gnu.org 2021-11-24 1:02 ` crazylht at gmail dot com 2021-12-15 12:47 ` jakub at gcc dot gnu.org 2021-12-16 1:27 ` crazylht at gmail dot com 2021-12-19 23:47 ` hjl.tools at gmail dot com
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-103194-4-5V9bBLR5JZ@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).