From: Torvald Riegel <triegel@redhat.com>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>
Cc: Ruslan Nikolaev <nruslan_devel@yahoo.com>,
nd@arm.com, Alexander Monakov <amonakov@ispras.ru>,
Florian Weimer <fweimer@redhat.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Fw: GCC interpretation of C11 atomics (DR 459)
Date: Tue, 27 Feb 2018 16:21:00 -0000 [thread overview]
Message-ID: <1519748155.15077.764.camel@redhat.com> (raw)
In-Reply-To: <4b2ab132-63e7-ce20-90e0-58632c60e07a@arm.com>
On Tue, 2018-02-27 at 13:04 +0000, Szabolcs Nagy wrote:
> the solutions is to add a language extension
I think this only needs a library interface, at least when we're just
considering the __atomic builtins. On the C/C++ level, it might amount
to just another atomic type, which only has a CAS however; this could be
probably modelled entirely through default atomics (not implemented
though), and so wouldn't need a language or memory model extension.
next prev parent reply other threads:[~2018-02-27 16:16 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1615980330.4453149.1519617655582.ref@mail.yahoo.com>
2018-02-26 4:01 ` Ruslan Nikolaev via gcc
2018-02-26 5:50 ` Alexander Monakov
2018-02-26 7:24 ` Fw: " Ruslan Nikolaev via gcc
2018-02-26 8:20 ` Alexander Monakov
2018-02-26 8:43 ` Ruslan Nikolaev via gcc
2018-02-26 19:07 ` Torvald Riegel
2018-02-26 19:43 ` Ruslan Nikolaev via gcc
2018-02-26 22:49 ` Ruslan Nikolaev via gcc
2018-02-27 3:33 ` Ruslan Nikolaev via gcc
2018-02-27 10:34 ` Ramana Radhakrishnan
2018-02-27 11:14 ` Torvald Riegel
2018-02-27 12:39 ` Torvald Riegel
2018-02-27 13:04 ` Ruslan Nikolaev via gcc
2018-02-27 13:08 ` Szabolcs Nagy
2018-02-27 13:17 ` Ruslan Nikolaev via gcc
2018-02-27 16:40 ` Torvald Riegel
2018-02-27 17:07 ` Ruslan Nikolaev via gcc
2018-02-27 16:21 ` Torvald Riegel [this message]
2018-02-27 16:16 ` Torvald Riegel
2018-02-27 16:46 ` Simon Wright
2018-02-27 16:52 ` Florian Weimer
2018-02-27 17:30 ` Torvald Riegel
2018-02-27 17:33 ` Ruslan Nikolaev via gcc
2018-02-27 19:32 ` Torvald Riegel
2018-02-27 17:59 ` Simon Wright
2018-02-27 10:40 ` Fw: " Torvald Riegel
2018-02-26 18:56 ` Torvald Riegel
2018-02-26 12:30 ` Szabolcs Nagy
2018-02-26 13:57 ` Alexander Monakov
2018-02-26 14:51 ` Szabolcs Nagy
2018-02-26 14:53 ` Ruslan Nikolaev via gcc
2018-02-26 18:35 ` Torvald Riegel
2018-02-26 18:59 ` Ruslan Nikolaev via gcc
2018-02-26 19:20 ` Torvald Riegel
2018-02-26 18:16 ` Florian Weimer
2018-02-26 18:34 ` Ruslan Nikolaev via gcc
2018-02-26 18:36 ` Janne Blomqvist
2018-02-27 10:22 ` Florian Weimer
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=1519748155.15077.764.camel@redhat.com \
--to=triegel@redhat.com \
--cc=amonakov@ispras.ru \
--cc=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=nd@arm.com \
--cc=nruslan_devel@yahoo.com \
--cc=szabolcs.nagy@arm.com \
/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).