Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (herse.apache.org: domain of ivan.volosyuk@gmail.com
 designates 64.233.162.233 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=ulnkcoOsDDns/ysjiI2FMeU5/egcYBTavQAaiC38C4mZyZUDHDHI9D6QP28JUJ4PnX9Ak/WI9IUYk9sHcyEANcm7+zaPjId4/D9s+W522rJdADJMg7HoZKB7KHntEWxJD1jl8ZyRwT7yrm9+nzubqLDNY3pQXuloxlXMQcb5ksc=
Message-ID: <12385bbd0611301545i2b518e6ehce280853686e6c2c@mail.gmail.com>
Date: Fri, 1 Dec 2006 02:45:52 +0300
From: "Ivan Volosyuk" <ivan.volosyuk@gmail.com>
To: dev@harmony.apache.org
Subject: Re: [drlvm][gcv5] is there an exclude list for "build test"?
In-Reply-To: <4dd1f3f00611301156s6dc93104mfef55c4b862b2f42@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4dd1f3f00611301156s6dc93104mfef55c4b862b2f42@mail.gmail.com>

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