IA64 xchg -- why only acquire?

IA64 xchg -- why only acquire?

Please illuminate.

regards,
alexander.

3 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

Alexander -

Are you wondering about why only acquire semantics? Or are you wondering why not release, instead?

For me, I think this operation requires both, but I have no idea why acquire was chosen. I've looked through the three Itanium programming books I have. Only one addresses this issue and only then to define it as an acquire operation.

I'll see if I can pass you inquiry on to someone else more versed in Itanium processors.

-- clay

ClayB wrote:
Alexander -Are you wondering about why only acquire semantics?

Yes. I need release and all sort of other msync semantics. And also "naked" (no msync) atomic stuff, to begin with. In my book, op.acquire is "equivalent" to op.(hoist_load+hoist_store) and release is nothing but op.(sinkt_load+sink_store). I need less constrained atomic "op"-stuff as well. See http://tinyurl.com/xky8 and http://tinyurl.com/xky9.

Leave a Comment

Please sign in to add a comment. Not a member? Join today