Andreas Zwinkau <zwin...@kit.edu> wrote on 03/04/2016 07:02:30 AM:
> From: Andreas Zwinkau <zwin...@kit.edu>
> To: x10-users@lists.sourceforge.net
> Date: 03/04/2016 07:03 AM
> Subject: [X10-users] Fences Java implementation
>
> The x10.util.concurrent.Fences implementation looks reasonable for C++,
> but the Java implementation seems weird to me.
>
> For example, loadLoadBarrier is implemented via two volatile reads. Why
> *two*? I could ask more questions ...
>
> The code was added by David Grove in 2009 it seems:
> https://github.com/x10-lang/x10/commit/
> f4f5420ce476f2538f358509ad13ef52b8c2c4c1
>
> Any idea where that came from? Any sources? Any reasons why it is the
> way it is?
Hi Andreas,
Best as I can remember, the Java code that is there was based on
discussion being had in 2009 about how to get memory fences given the
definition of the Java memory model and java.util.concurrent as it existed
at the time.
--dave
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
X10-users mailing list
X10-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/x10-users
