- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please illuminate.
regards,
alexander.
regards,
alexander.
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page