Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
comp.programming.threads
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion Memory Barriers, Compiler Optimizations, etc.
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Alexander Terekhov  
View profile  
 More options Feb 5 2005, 8:17 am
Newsgroups: comp.programming.threads
From: Alexander Terekhov <terek...@web.de>
Date: Sat, 05 Feb 2005 14:17:07 +0100
Local: Sat, Feb 5 2005 8:17 am
Subject: Re: Memory Barriers, Compiler Optimizations, etc.
Print | View thread | Show original | Report this message | Find messages by this author

Ziv Caspi wrote:

[...]

> Microsoft has already provided some guarantees here, as specified in
> http://www.microsoft.com/whdc/driver/kernel/MP_issues.mspx. In particular,
> it treats volatile reads as having acquire semantics, and volatile writes as
> having release semantics, so if you target CL 14 (or later), you have a
> solution.

I doubt it. KeMemoryBarrier* idiocy and braindead illustrations from
that piece speak volumes to the contrary.

regards,
alexander.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google