public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "spop at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/105162] [AArch64] outline-atomics drops dmb ish barrier on __sync builtins Date: Mon, 18 Apr 2022 15:20:12 +0000 [thread overview] Message-ID: <bug-105162-4-hFpC4BOG7E@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105162-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105162 Sebastian Pop <spop at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #52762|0 |1 is obsolete| | --- Comment #8 from Sebastian Pop <spop at gcc dot gnu.org> --- Created attachment 52826 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52826&action=edit patch You are right. Please see attached an amended patch that only adds the barriers to __sync builtins.
next prev parent reply other threads:[~2022-04-18 15:20 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-05 15:29 [Bug target/105162] New: " spop at gcc dot gnu.org 2022-04-05 16:55 ` [Bug target/105162] " spop at gcc dot gnu.org 2022-04-05 16:56 ` spop at gcc dot gnu.org 2022-04-05 21:18 ` spop at gcc dot gnu.org 2022-04-06 15:03 ` spop at gcc dot gnu.org 2022-04-06 21:55 ` spop at gcc dot gnu.org 2022-04-07 8:47 ` ktkachov at gcc dot gnu.org 2022-04-14 11:22 ` wilco at gcc dot gnu.org 2022-04-18 15:20 ` spop at gcc dot gnu.org [this message] 2022-05-13 17:11 ` cvs-commit at gcc dot gnu.org 2022-05-16 13:18 ` cvs-commit at gcc dot gnu.org 2022-05-16 14:40 ` cvs-commit at gcc dot gnu.org 2022-05-16 14:42 ` cvs-commit at gcc dot gnu.org 2022-05-16 14:44 ` cvs-commit at gcc dot gnu.org 2022-05-16 14:59 ` spop at gcc dot gnu.org 2022-10-27 2:28 ` pinskia at gcc dot gnu.org 2022-10-27 2:30 ` [Bug target/105162] [9/10/11/12/13 Regression] " pinskia 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-105162-4-hFpC4BOG7E@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).