United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
JDK-6624474 : Server compiler generates unexpected LinkageError

Details
Type:
Bug
Submit Date:
2007-10-31
Status:
Resolved
Updated Date:
2010-04-02
Project Name:
JDK
Resolved Date:
2008-06-25
Component:
hotspot
OS:
solaris_10
Sub-Component:
compiler
CPU:
x86
Priority:
P2
Resolution:
Fixed
Affected Versions:
5.0u10
Fixed Versions:
hs13 (b01)

Related Reports
Backport:
Backport:
Relates:
Relates:

Sub Tasks

Description
Customer Note -
Here's a microbenchmark which throws a LinkageError on X86 -server but runs fine with -client and -Xint.
I'm not sure why it throws the LinkageError; it works fine on our version of -server.
I'm not all that sure what the proper behavior should be, but I suspect the LinkageError isn't correct.

I have enclosed their tar file.(see attachments)

                                    

Comments
EVALUATION

Before compiling, in CompileBroker:compile_method(), the server compiler resolves
string constants and loads signature classes.  C1 does not do this. 

The failure occurs as we prepare to compile from_loader2.gen.
                                     
2007-11-01
EVALUATION

The server compiler is slightly more eager in loading classes than the client
compiler or the interpreter.  The function load_signature_classes() called to
resolve classes associated with the signature of the method being compiled.

The test case provided is an example where a LinkageError is thrown on the eager
class loading.  See bug 4944478 for a similar case where a ClassNotFoundException
was thrown.
                                     
2007-11-05
EVALUATION

load_signature_classes() should ignore LinkageErrors.
                                     
2007-11-06



Hardware and Software, Engineered to Work Together