The test you described has a lot of hidden issues. For example: if Sun supports such situation only with interpreter (need to investigate), may be it's enough if we support it only with JET (in the default mode JET compiles all methods first)? In this case if we see ClassCircularityError in OPT we have a chance to return JIT_FAILURE to EM and ask EM to compile this method with JET?
On 10/11/06, Pavel Pervov <[EMAIL PROTECTED]> wrote:
I suspect it was JRockit java, which crashed. Since Sun's jvm is hotspot, you have to force it into compiling the method. Otherwise it will interpret the method and everything will work fine. :) Pavel. On 10/11/06, Mikhail Fursov <[EMAIL PROTECTED]> wrote: > > Will this test pass on SUN or BEA JVM? > I remember I tried something similar but one of the RIs crashed :) > > On 10/11/06, Pavel Pervov <[EMAIL PROTECTED]> wrote: > > > > (Branching from original thread as this is different problem than in the > > root message.) > > > > Mikhail, > > > > The following scenario will fail: > > > > 1) JIT compiles some method and resolves some class "A" through user > > defined > > class loader > > 2) user define class loader loads class "A" and triggers compilation of > > some > > of its methods > > 3) this method happens to depend on class "A", and, thus, JIT resolves > the > > class "A" through the same class loader > > > > Voila! We have the described situation. > > > > Regards, > > Pavel. > > > > > > > -- > Mikhail Fursov > >
-- Mikhail Fursov
