Change the atomics used in DefaultAssociativeDom into explicit processor atomics
Change the atomics used in DefaultAssociativeDom into explicit processor atomics

[reviewed by gbt]

This commit makes the atomics used for numEntries and tableLock in
DefaultAssociativeDom explicit processor atomics.  DefaultAssociative
is a single locale domain map, and, at least currently, it is used
primarily from the locale on which it allocated.  Note that by design,
the algorithms used are cognizant of the fact that processor atomics
are being used and there are explicit on clauses sprinkled throughout
the code.  If I were doing this with network AMOs, there's a good
chance I'd want to do something a bit different.



git-svn-id: 88467cb1fb04b8a755be7e1ee1026be4190196ef@20341 3a8e244f-b0f2-452b-bcba-4c88e055c3ca

chizarlicious/chapel,CoryMcCartan/chapel,sungeunchoi/chapel,hildeth/chapel,hildeth/chapel,chizarlicious/chapel,sungeunchoi/chapel,CoryMcCartan/chapel,hildeth/chapel,CoryMcCartan/chapel,sungeunchoi/chapel,CoryMcCartan/chapel,sungeunchoi/chapel,hildeth/chapel,chizarlicious/chapel,CoryMcCartan/chapel,hildeth/chapel,chizarlicious/chapel,hildeth/chapel,sungeunchoi/chapel,chizarlicious/chapel,CoryMcCartan/chapel,sungeunchoi/chapel,chizarlicious/chapel,hildeth/chapel,chizarlicious/chapel,CoryMcCartan/chapel,sungeunchoi/chapel,sungeunchoi/chapel