RFR(M) 8138894: C1: Support IRIW on weak memory platforms

[Christian Thalinger]

> On Oct 19, 2015, at 11:02 PM, Doerr, Martin <martin.doerr at sap.com> wrote:
> 
> Hi Christian,
>  
> can I consider this change reviewed?

Yes.

> You had a look at it in your reply to my email announcing the C1 PPC64 port. Your reply:
> http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2015-October/019220.html <http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2015-October/019220.html>
>  
> Thanks,
>   Martin
>  
>  
> From: Doerr, Martin 
> Sent: Donnerstag, 8. Oktober 2015 23:47
> To: 'hotspot compiler'
> Subject: RFR(M) 8138894: C1: Support IRIW on weak memory platforms
>  
> Hi,
>  
> Some time ago, we implemented support for ordering of "Independent Reads of Independent Writes" in the template interpreter and C2 Compiler for PPC64. However, it needs to be consistent with C1.
>  
> Without "IRIW" support, we generate load-acquire for volatile loads and release-store-fence for volatile stores.
> With "IRIW" support, we generate fence-load-acquire for volatile loads and release-store for volatile stores.
> CPU_NOT_MULTIPLE_COPY_ATOMIC is currently only defined on PPC64 (though it may be interesting for aarch64 as well).
> This change is a prerequisite for our C1 on PPC64 contribution.
>  
> Webrev is here:
> http://cr.openjdk.java.net/~mdoerr/8138894_c1_IRIW/webrev.00 <http://cr.openjdk.java.net/~mdoerr/8138894_c1_IRIW/webrev.00>
>  
> Please review this change.  I need a sponsor, please.
>  
> Best regards,
>   Martin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/attachments/20151020/d183834c/attachment-0001.html>