Subj : Re: What does Memory Barriers mean ??
To   : comp.programming.threads
From : David Schwartz
Date : Tue Jan 11 2005 01:07 am


"SenderX" <xxx@xxx.com> wrote in message 
news:6oydnQh3m8v4FX7cRVn-vg@comcast.com...

>> No. Calling an assembly routine, unless it is a standard library 
>> function,
>> already causes undefined behaviour according to the standards.

> Yes. The calling convention is an issue.

    You guys are construing "standards" very narrowly. When I say 
"standards", I mean all the relevant documentation that accompanies all the 
interfaces and extensions you are using. If you use GCC's inline assembly 
correctly, according to the documentation, your code will work perfectly at 
every level of optimization without you having to do anything other than 
correctly follow the documentation. Black magic is not needed.

    DS

.