public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/103194] New: ice in optimize_atomic_bit_test_and, at tree-ssa-ccp.c:3626 Date: Thu, 11 Nov 2021 16:48:55 +0000 [thread overview] Message-ID: <bug-103194-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103194 Bug ID: 103194 Summary: ice in optimize_atomic_bit_test_and, at tree-ssa-ccp.c:3626 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- For this C code: long pscc_a_2_3; int pscc_a_1_4; void pscc() { pscc_a_1_4 = __sync_fetch_and_and(&pscc_a_2_3, 1); } compiled by recent gcc trunk, does this: $ /home/dcb/gcc/results/bin/gcc -c -O1 bug771.c during GIMPLE pass: fab bug771.c: In function ‘pscc’: bug771.c:3:6: internal compiler error: in optimize_atomic_bit_test_and, at tree-ssa-ccp.c:3626 3 | void pscc() | ^~~~ 0xee6020 optimize_atomic_bit_test_and(gimple_stmt_iterator*, internal_fn, bool, bool) ../../trunk.git/gcc/tree-ssa-ccp.c:3626 0xee389a (anonymous namespace)::pass_fold_builtins::execute(function*) ../../trunk.git/gcc/tree-ssa-ccp.c:0 The bug first seems to occur sometime between git hash f2572a398d21fd52 and a97fdde627e64202,a distance of some 60 commits. In that range, commit fb161782545224f55ba26ba663889c5e6e9a04d1 looks a likely candidate.
next reply other threads:[~2021-11-11 16:48 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-11 16:48 dcb314 at hotmail dot com [this message] 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 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@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).