From: Andrew MacLeod <amacleod@redhat.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>, gcc-patches@gcc.gnu.org
Subject: Re: Implement C11 _Atomic
Date: Fri, 22 Nov 2013 03:03:00 -0000 [thread overview]
Message-ID: <528E97EC.9070107@redhat.com> (raw)
In-Reply-To: <alpine.BSF.2.02.1311211758050.26167@arjuna.pair.com>
On 11/21/2013 06:23 PM, Hans-Peter Nilsson wrote:
> On Thu, 21 Nov 2013, Andrew MacLeod wrote:
>> I can bootstrap and check this on x86 to make sure it doesnt affect anything,
>> and you can fool with it and see if you can get your desired results with your
>> port.
> Success!
>
> For the record, tested together with the attached patch for the
> CRIS ports, both regularly (not finished, but done with the C
> testsuite part and no regressions there), as well as manually
> for the attached test-programs, compiling and inspecting output
> for different sub-targets and checking that data layout,
> alignment and size is as intended.
>
> Too bad about the libstdc++ atomics, but with this/these patches
> at least I'll be able to tell people that _Atomic for C11 works.
>
> Thanks to the both of you!
>
>
All we need is a way to communicate the atomic property to the type
within the libstdc++ template... We cant use _Atomic there :-P
I originally had created an __attribute__ ((atomic)) whch you could
apply to the atomic template type and get the same behaviour as
_Atomic, Im not sure if there is another way or not. The atomic
template is generic, so I couldn't think of any special macro wizardry
we could define...
Andrew
next prev parent reply other threads:[~2013-11-21 23:32 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
2013-11-21 19:24 ` Hans-Peter Nilsson
2013-11-22 2:57 ` Hans-Peter Nilsson
2013-11-22 3:03 ` Andrew MacLeod [this message]
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=528E97EC.9070107@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).