public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/114310] [11/12/13/14 Regression] [aarch64] __sync_val_compare_and_swap fails on __int128_t with newval = 0 Date: Tue, 12 Mar 2024 00:13:54 +0000 [thread overview] Message-ID: <bug-114310-4-43kLQVhZVx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114310-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114310 Jeffrey A. Law <law at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |law at gcc dot gnu.org --- Comment #2 from Jeffrey A. Law <law at gcc dot gnu.org> --- !?! That doesn't make any sense to me Andrew. This is a failure to match the insn, not a constraint error. And given the existence of a zero register, isn't zero valid anywhere a general purpose register is valid?
next prev parent reply other threads:[~2024-03-12 0:13 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-11 17:48 [Bug c/114310] New: " p.nguyen at yahooinc dot com 2024-03-11 18:01 ` [Bug target/114310] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org 2024-03-12 0:13 ` law at gcc dot gnu.org [this message] 2024-03-12 0:25 ` pinskia at gcc dot gnu.org 2024-03-12 12:03 ` rguenth at gcc dot gnu.org 2024-03-13 18:13 ` jakub at gcc dot gnu.org 2024-03-14 13:10 ` cvs-commit at gcc dot gnu.org 2024-03-14 15:34 ` [Bug target/114310] [11/12/13 " jakub at gcc dot gnu.org 2024-03-15 23:29 ` cvs-commit at gcc dot gnu.org 2024-03-18 14:41 ` [Bug target/114310] [11/12 " 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-114310-4-43kLQVhZVx@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).