RFR (M): 8143925: Enhancing CounterMode.crypt() for AES

John Rose john.r.rose at oracle.com
Wed Jan 6 17:42:44 UTC 2016

On Jan 6, 2016, at 4:20 AM, Vitaly Davidovich <vitalyd at gmail.com> wrote:
> I realize that there may always be a user-specified shape that the JIT doesn't understand, but straightforward cases should hopefully Just Work(tm) as those patterns can be picked up elsewhere in code and performance improves without changing a line of code.

Where we differ is this:  I am skeptical that there is a well-defined set of "straightforward cases", which all reasonable coders, who expect optimization, will use.

It is better to point out one case for favorable treatment, and say "if you really expect best optimization, use this name".  Followed by, "if you don't choose to use that name, we'll still try to optimize all the straightforward cases, but don't expect us to prioritize them as highly as the best practice we suggested".

— John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/attachments/20160106/3b4a1e81/attachment.html>

More information about the hotspot-compiler-dev mailing list