Hi Sara --
The compound 'atomic' statement you refer to above never made it onto the master branch of the Chapel implementation, unfortunately (and therefore not into any releases). If I recall correctly, we were lacking a portable implementation of atomic variables at that time (this was prior to C and C++ adopting them) and, as often happens, the student had to focus on finishing his degree and finding a job over getting his software into shape to merge onto master. Shortly thereafter, we added atomic types to the language and haven't returned to this more general compound statement form since then. But to answer your question, yes, the intention was that the atomic block would work even across locales / distributed memory. -Brad ________________________________ From: Sara Salem Hamouda <[email protected]> Sent: Friday, November 18, 2016 10:25:10 PM To: [email protected] Subject: Cross-locale atomic blocks Hi Chapel team and users, Can an atomic block in chapel cross places? In other words, in the following allowed in Chapel: atomic { on Locale(1) { .... } on Locale(2) { .... } } I read the PPoPP'08 paper that describes a distributed software transactional memory solution for Chapel (http://dl.acm.org/citation.cfm?id=1345242). Was this solution included in any Chapel release? Thank you, Sara Sara S. Hamouda PhD Candidate Australian National University
------------------------------------------------------------------------------
_______________________________________________ Chapel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-users
