public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/80878] -mcx16 (enable 128 bit CAS) on x86_64 seems not to work on 7.1.0
Date: Fri, 07 May 2021 14:07:57 +0000	[thread overview]
Message-ID: <bug-80878-4-dQLy4kstB0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-80878-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80878

--- Comment #34 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Niall Douglas from comment #33)
> Re: your original point, I cannot say anything about _Atomic. However, for
> std::atomic<__int128>, as __int128 is not an integral type it seems

That depends whether you use -std=c++NN or -std=gnu++NN

> reasonable to me that its specialisation tell the compiler to not store it
> in read only memory. Mark it with attribute section, give it a non-trivial
> destructor, or whatever it needs.

std::atomic<T> requires T to have a trivial destructor, so the destructor is
always trivial.

> Perhaps I ought to open a separate issue here, as my specific problem is
> that std::atomic<__int128>::compare_exchange_weak() is not using cmpxchg16b?

Isn't that covered by PR 94649?

std::atomic just calls the relevant __atomic built-in for all operations. What
the built-in does is not up to libstdc++.

  parent reply	other threads:[~2021-05-07 14:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-80878-4@http.gcc.gnu.org/bugzilla/>
2020-04-18 17:14 ` avi@cloudius-systems.com
2020-04-18 17:23 ` fw at gcc dot gnu.org
2020-04-18 17:31 ` avi@cloudius-systems.com
2020-04-18 17:40 ` fw at gcc dot gnu.org
2020-04-18 18:13 ` avi@cloudius-systems.com
2020-04-18 18:18 ` avi@cloudius-systems.com
2020-04-18 18:41 ` fw at gcc dot gnu.org
2021-03-14  3:21 ` wuyongwei at gmail dot com
2021-03-14  3:46 ` wuyongwei at gmail dot com
2021-03-16 16:02 ` wuyongwei at gmail dot com
2021-05-06 17:50 ` s_gccbugzilla at nedprod dot com
2021-05-06 19:32 ` pinskia at gcc dot gnu.org
2021-05-06 20:53 ` liblfds_gccbz at winterflaw dot net
2021-05-07 12:27 ` s_gccbugzilla at nedprod dot com
2021-05-07 14:07 ` redi at gcc dot gnu.org [this message]
2021-05-07 14:44 ` s_gccbugzilla at nedprod dot com
2022-11-03  9:55 ` lh_mouse at 126 dot com
2022-11-03 10:04 ` jakub at gcc dot gnu.org
2022-11-03 10:32 ` fw at gcc dot gnu.org
2022-11-03 11:16 ` admin_public at liblfds dot org
2023-11-16  1:33 ` lh_mouse at 126 dot com
2023-12-10  9:54 ` lh_mouse at 126 dot com
2023-12-10 10:32 ` admin_public at liblfds dot 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-80878-4-dQLy4kstB0@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: link
Be 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).