From: Olaf Hering <olh@suse.de>
To: Greg Smith <gsmith@nc.rr.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [OT] ppc64 serialization problem
Date: Wed, 29 Mar 2006 20:32:59 +0200 [thread overview]
Message-ID: <20060329183259.GA18514@suse.de> (raw)
In-Reply-To: <1143656433.3075.108.camel@localhost.localdomain>
On Wed, Mar 29, Greg Smith wrote:
> So it is clear between .A and .B -> value of b was read then written. If
> anything happens between .A and .B to ->b, then it is lost.
Even gcc4.1 does it that way with -O0.
next prev parent reply other threads:[~2006-03-29 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 1:58 [OT] ppc64 serialization problem Greg Smith
2006-03-29 3:11 ` Benjamin Herrenschmidt
2006-03-29 4:08 ` Greg Smith
2006-03-29 4:21 ` Benjamin Herrenschmidt
2006-03-29 4:07 ` Paul Mackerras
2006-03-29 18:20 ` Greg Smith
2006-03-29 18:32 ` Olaf Hering [this message]
2006-03-29 18:42 ` Ivan Warren
2006-03-29 21:29 ` Ivan Warren
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=20060329183259.GA18514@suse.de \
--to=olh@suse.de \
--cc=gsmith@nc.rr.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.