|
Quick Lists
|
|
Bug ID:
|
6624474
|
|
Votes
|
0
|
|
Synopsis
|
Server compiler generates unexpected LinkageError
|
|
Category
|
hotspot:compiler2
|
|
Reported Against
|
|
|
Release Fixed
|
hs13(b01)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
2-High
|
|
Related Bugs
|
4944478
|
|
Submit Date
|
31-OCT-2007
|
|
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)
Posted Date : 2007-10-31 21:56:02.0
|
|
Work Around
|
N/A
|
|
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.
Posted Date : 2007-11-01 22:47:22.0
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.
Posted Date : 2007-11-05 23:52:15.0
load_signature_classes() should ignore LinkageErrors.
Posted Date : 2007-11-06 00:01:25.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |