JDK-6251998 : client compiler does not inline primitive_arraycopy
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 5.0
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2005-04-07
  • Updated: 2011-04-05
  • Resolved: 2011-04-05
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 7
7Resolved
Related Reports
Duplicate :  
Description
During the analysis of the startup time of Netbeans, it
was noticed that the client compiler was calling the VM service 
Runtime1::primitive_arraycopy over 1 million times.

The server compiler chose to inline this operation in order to
eliminate the argument passing and call overhead for this 
frequently used service.

Unfortunately, the Forte analyzer does not report the time spent in
this specific function.  Since it is called from compiled code, the
time spent in this service is spead throughout all of the compiled
methods that use it.

The RFE is requesting that some other tool such as DTRACE be used to 
identify the potential cost savings and then implement some inlining
in the client compiler if this analysis justifies it.


###@###.### 2005-04-07 14:44:19 GMT

Comments
EVALUATION This doesn't actually help startup though it does help performance somewhat on linux. I may try to get approval for mustang but for now I'm retargeting to dolphin.
23-05-2006

EVALUATION There was various improvements to the internal version of the arraycopy stubs and C1 should start using them. Additionally we should attempt to eliminate most tests in the fast case.
13-03-2006