public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit 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, 16 May 2022 14:42:42 +0000 [thread overview] Message-ID: <bug-105162-4-B8fdAjcDnN@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 --- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Sebastian Pop <spop@gcc.gnu.org>: https://gcc.gnu.org/g:9ef808fb4373c8d8479539cb19ae00b1bcec87ea commit r11-10005-g9ef808fb4373c8d8479539cb19ae00b1bcec87ea Author: Sebastian Pop <spop@amazon.com> Date: Mon Apr 18 15:13:20 2022 +0000 [AArch64] add barriers to ool __sync builtins 2022-05-13 Sebastian Pop <spop@amazon.com> gcc/ PR target/105162 * config/aarch64/aarch64-protos.h (atomic_ool_names): Increase dimension of str array. * config/aarch64/aarch64.c (aarch64_atomic_ool_func): Call memmodel_from_int and handle MEMMODEL_SYNC_*. (DEF0): Add __aarch64_*_sync functions. gcc/testsuite/ PR target/105162 * gcc.target/aarch64/sync-comp-swap-ool.c: New. * gcc.target/aarch64/sync-op-acquire-ool.c: New. * gcc.target/aarch64/sync-op-full-ool.c: New. * gcc.target/aarch64/target_attr_20.c: Update check. * gcc.target/aarch64/target_attr_21.c: Same. libgcc/ PR target/105162 * config/aarch64/lse.S: Define BARRIER and handle memory MODEL 5. * config/aarch64/t-lse: Add a 5th memory model for _sync functions.
next prev parent reply other threads:[~2022-05-16 14:42 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 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 [this message] 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-B8fdAjcDnN@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).