From: Richard Henderson <rth@redhat.com>
To: Andrew MacLeod <amacleod@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [cxx-mem-model] Atomic C++ header file changes
Date: Fri, 19 Aug 2011 04:05:00 -0000 [thread overview]
Message-ID: <4E4D9349.30702@redhat.com> (raw)
In-Reply-To: <4E4BE0BE.8000901@redhat.com>
On 08/17/2011 08:39 AM, Andrew MacLeod wrote:
> ! return __sync_mem_load (const_cast <__int_type *>(&_M_i), __m);
This suggests the builtin is incorrectly defined.
It ought to be const itself.
r~
next prev parent reply other threads:[~2011-08-18 22:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 17:54 Andrew MacLeod
2011-08-19 4:05 ` Richard Henderson [this message]
2011-08-23 23:24 ` Andrew MacLeod
2011-08-24 1:07 ` Richard Henderson
2011-08-24 3:09 ` Andrew MacLeod
2011-08-24 6:41 ` Richard Henderson
2011-08-19 10:17 ` Torvald Riegel
2011-08-19 13:22 ` Andrew MacLeod
2011-08-19 19:12 ` Torvald Riegel
2011-08-19 21:11 ` Andrew MacLeod
2011-08-24 17:25 ` Andrew MacLeod
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=4E4D9349.30702@redhat.com \
--to=rth@redhat.com \
--cc=amacleod@redhat.com \
--cc=gcc-patches@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).