harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiao-Feng Li" <xiaofeng...@gmail.com>
Subject Re: [drlvm][gcv5] is there an exclude list for "build test"?
Date Fri, 01 Dec 2006 00:32:30 GMT
Agree with Ivan, probably this next-to-high-bit thing is outdated, I
remember Mikail Fursov said the finalize property will be checked
outside the allocation invocation.  (So agree with Gregory as well
this may have nothing to do with JVMTI.)

Thanks,
xiaofeng

On 12/1/06, Ivan Volosyuk <ivan.volosyuk@gmail.com> wrote:
> Most probably it should be an object with finalize() method. This was
> done to prevent fast path allocation for such objects. This is a very
> old code.
> --
> Ivan
>
> On 11/30/06, Weldon Washburn <weldonwjw@gmail.com> wrote:
> > Xiao Feng,
> >
> > It would be great if you could publish something like a list of what tests
> > run.   I tried to run "build test" on windowsxp 32 w/ gcv5.  It looks like
> > all the [jvmti] tests using the JIT pass.  For some yet to be discovered
> > reason, the test suite fails when it runs the JVMTI  breakpoint1 test w/
> > interpreter.
> > Incidentally, the test causes GCV5 to execute an assert(0) that seems rather
> > strange.  assert(0); on line 52 of lspace.cpp is hit.  The size of the
> > object requested is: 0x40000018.   This looks like it is a request to create
> > an object that follows the conventions in Class.h.   That is, Class.h line
> > 883 says, "The next to high bit is set if allocation needs to consider
> > class_properties."  However, the comment in lspace.cpp says, /* FIXME::
> > trigger collection */.  Its probably not a situation that warrents a
> > collection but instead a request for uncommon object attribute such as
> > pinning maybe (??)
> >
> > Weldon Washburn
> > Intel Enterprise Solutions Software Division
>
> --
> Ivan
> Intel Enterprise Solutions Software Division
>

Mime
View raw message