public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/115188] [14/15 regression] invalid Thumb assembly for atomic store in loop on ARMv6 Date: Wed, 22 May 2024 18:39:01 +0000 [thread overview] Message-ID: <bug-115188-4-KQhgTwEgLw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115188-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115188 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=115153, | |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=111235 Target|arm |arm-eabi --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- At first I thought it was the same failure as PR 115153 but it is different.
next prev parent reply other threads:[~2024-05-22 18:39 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-22 14:06 [Bug target/115188] New: " ebotcazou at gcc dot gnu.org 2024-05-22 14:07 ` [Bug target/115188] " rguenth at gcc dot gnu.org 2024-05-22 18:39 ` pinskia at gcc dot gnu.org [this message] 2024-05-23 14:22 ` wilco 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-115188-4-KQhgTwEgLw@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).