From: Andrew MacLeod <amacleod@redhat.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Hans-Peter Nilsson <hp@bitrange.com>, gcc-patches@gcc.gnu.org
Subject: Re: Implement C11 _Atomic
Date: Thu, 21 Nov 2013 18:58:00 -0000 [thread overview]
Message-ID: <528E3997.7080401@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1311211629360.19332@digraph.polyomino.org.uk>
On 11/21/2013 11:32 AM, Joseph S. Myers wrote:
> On Thu, 21 Nov 2013, Andrew MacLeod wrote:
>
>>> I'm trying to avoid ABI breakage of course. I'd rather not have
>>> to ask people not to use _Atomic with 4.9 for CRIS ports using
>>> official releases or have ABI breakage with the next release.
>>> Maybe there's one other port in the same situation...
>> None I am aware of, but that doesn't mean much :-)
> It has been suggested that hppa may have interesting issues for atomics -
> but I'd think atomics support for it in GCC would mainly be for GNU/Linux,
> where you have kernel helpers that may avoid the issues with the
> underlying architecture.
>
> Note that if you want libstdc++ atomics to be ABI compatible with C
> atomics then there may be more work to do on that side (again, there are
> pieces on the branch).
>
I was just about to point out that :-) that would be a
shortcoming... 4.9 C++11 atomics do not use the same mechanism yet, so
they would still behave the same as 4.8 C++ atomics, even with the
override present.... C11 _Atomic variables would be the only beneficiary
at this point of the override.
Andrew
next prev parent reply other threads:[~2013-11-21 16:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 0:44 Joseph S. Myers
2013-11-06 22:42 ` Andrew MacLeod
2013-11-07 17:16 ` Uros Bizjak
2013-11-07 17:24 ` Jakub Jelinek
2013-11-07 18:10 ` Uros Bizjak
2013-11-07 18:44 ` Joseph S. Myers
2013-11-07 18:47 ` Uros Bizjak
2013-11-07 18:55 ` Joseph S. Myers
[not found] ` <CAFULd4ZrAEECG+pptH8cRaWznioaM9VXS4TetpEvkWj--n7H1w@mail.gmail.com>
2013-11-07 21:02 ` Joseph S. Myers
2013-11-07 21:08 ` Uros Bizjak
2013-11-07 22:25 ` Uros Bizjak
2013-11-07 22:43 ` Joseph S. Myers
2013-11-08 10:09 ` Uros Bizjak
2013-11-08 13:33 ` Joseph S. Myers
2013-11-21 13:19 ` Hans-Peter Nilsson
2013-11-21 18:03 ` Andrew MacLeod
2013-11-21 18:20 ` Hans-Peter Nilsson
2013-11-21 18:30 ` Andrew MacLeod
2013-11-21 18:49 ` Joseph S. Myers
2013-11-21 18:58 ` Andrew MacLeod [this message]
2013-11-21 19:24 ` Hans-Peter Nilsson
2013-11-22 2:57 ` Hans-Peter Nilsson
2013-11-22 3:03 ` Andrew MacLeod
2013-11-22 3:32 ` Hans-Peter Nilsson
2013-11-22 3:32 ` Joseph S. Myers
2013-11-22 19:12 ` Andrew MacLeod
2013-11-22 20:01 ` Hans-Peter Nilsson
2013-11-08 13:28 Dominique Dhumieres
2013-11-08 13:34 ` Joseph S. Myers
2013-11-08 13:43 ` Dominique Dhumieres
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=528E3997.7080401@redhat.com \
--to=amacleod@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@bitrange.com \
--cc=joseph@codesourcery.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).