Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 5 Feb 2003 16:01:11 +0200
From:      Alexey Zelkin <phantom@FreeBSD.org.ua>
To:        Brent Verner <brent@rcfile.org>
Cc:        freebsd-java@FreeBSD.ORG
Subject:   Re: patchset 2 report (a love story)
Message-ID:  <20030205160111.A89218@phantom.cris.net>
In-Reply-To: <20030205121006.GA69850@rcfile.org>; from brent@rcfile.org on Wed, Feb 05, 2003 at 07:10:06AM -0500
References:  <20030205121006.GA69850@rcfile.org>

next in thread | previous in thread | raw e-mail | index | archive | help
hi,

On Wed, Feb 05, 2003 at 07:10:06AM -0500, Brent Verner wrote:
> Hi,
> 
>   After a long 6 hour compile that ended in a failure on a plugin

Not good, plugin build is completely disabled for now...  I'll take a
look.

BTW, if you've fast machine with enough memory you may try to build
hotspot object files parallely:

setenv HOTSPOT_BUILD_JOBS 4

before starting the build (for example)

> target, I had a fresh native 1.4.1 image (with HotSpot no less!)

Sorry, there's no support for something other than HotSpot in JDK 1.4 :-)

> for my 4.7-stable box.  I've been running a couple of tomcat apps 
> pretty heavily for the past few hours, and things seem stable, aside 
> from a few DEBUG: signal messages[1].  Aside from apparent stability, 
> the performance improvement over native 1.3.1 is about 600%.  
> Nice work.

Cool!

>   Now, a nit... I tried building on a -current machine, but the
> 3.2.1 compiler bails early in the build of adlc, complaining of
> numerous ostream operator link-errors.  I hacked around with 
> this a bit, while the 4.7 box was building, but gave up after
> I noticed that I could compile the same ostream<<(char) code 
> that the build was complaining about.  Weird.

Strange.  Can you please provide me information about exact error
messages, 'gcc -v', and 'uname -a' ?

>   In any case, kudos Alexey, for the fine work.  If there is any
> legwork that I could do in getting 3.2.1 compiling on -current,
> let me know; I'd be glad to help.

Provide me details on failure, please.

>   I created a ports directory for the jdk14, and was wondering if 
> it would be possible to distribute patchset 2 in .zip format, so
> USE_ZIP could be set in the Makefile to extract both the scsl-src
> and patchset, instead of having to _manually_ extract one of them.
> If I'm missing some feature of the ports system that would allow
> automatic extraction of both, please throw that cluestick at me :-)

I'd like to look.  I think Greg too :)

>   On the HotSpot note, is there any work being done on getting 1.3.1's
> HotSpot working?  AFAIR, it would not build with 1.3.1-patchset-7.

Yes.  Patchset 8 for 1.3.1 will appear soon...  Greg ?

> [1] one of these is signal 11, so if this is _the_ signal 11ôI'm
>     familiar with, and you want to know how to duplicate, I could
>     probably distill a testcase.

It's debug printf, signal 11 is indicating that something goes wierd
inside java compiled code.  But since you don't see any exception or
fatal failures -- JVM is able to recover from this problem.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-java" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030205160111.A89218>