JDK-8169201 : Montgomery multiply intrinsic should use correct name
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 9
  • Priority: P5
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2016-11-03
  • Updated: 2019-01-14
  • Resolved: 2016-11-11
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8 JDK 9
8u181Fixed 9 b150Fixed
Related Reports
Relates :  
JDK-8130150 - Implement BigInteger.montgomeryMultiply intrinsic
Description
The inline_montgomeryMultiply() instrinsic uses "montgomery_square" as stubName, as can be observed here:

http://hg.openjdk.java.net/jdk9/hs/hotspot/file/8c2f220c759c/src/share/vm/opto/library_call.cpp#l5508

This seems like a minor bugs, because the stubName is not used for anything important (only to identify the call in escape analysis, and there it's ok to use one or the other afaict).
Comments
RFR - http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2016-November/024899.html
10-11-2016
ILW = Stub call uses wrong stub name (no affect on correctness/performance), only with the montgomery intrinsic, no workaround = LMH = P5
09-11-2016