HotSpot 14

Andrew John Hughes gnu_andrew at
Fri May 15 11:29:08 PDT 2009

2009/5/15 Erik Trimble <Erik.Trimble at>:
> Andrew John Hughes wrote:
>> Hi all (especially Joe),
>> Now that the HotSpot Express repositories are available, what is the
>> plan for including hs14 in OpenJDK6?
>> I did a pull of the base changeset from HS express (0) into OpenJDK6's
>> hotspot repo. yesterday as a test, and it seems to apply fairly well.
>> The conflicts all seem to be whitespace changes (though there's a lot
>> of them -- ~210 files are affected).
>> Do we still plan to maintain a version of HotSpot in OpenJDK6 or will
>> HS Express just be used directly?
>> Thanks,
> Frankly, I think this is up to the Community.
> I'm still not 100% sure of the complete list of who has write access to the
> OpenJDK6 stuff, but I /think/ the proper way to do this is not move any HSX
> release into the main OpenJDK6 forest until there is  consensus that It's
> Time.

The list is here: for your
delectation and delight.

> Now, that said, maybe It's Time Right Now.

IcedTea (i.e. the version of OpenJDK6 people are actually using on
their distros today) has already been shipping HotSpot 14 for some
time.  So I think not only is the time right for OpenJDK6 upstream to
also upgrade, but that it's perhaps long overdue.

> Given that the HSX repos are going to be almost exclusively Sun-only
> writable (in practice, not necessarily by design), I think that the VM in
> OpenJDK6 should be pulled from an HSX repo, and then have various
> community-desired patches applied there, rather than try to work directly on
> an HSX repo.  That is, I expect the various HSX repos to be a reflection of
> what Sun is doing, and the VM in OpenJDK6 should be a reflection of what the
> Community chooses to do with the HSX work from Sun.

My preference would be for patches to go into HotSpot Express and then
OpenJDK6 just pull a stable version regularly.  I've already had
patches committed to HotSpot as have others working on IcedTea, so I
don't see an issue there.

> As such, going forward, I _hope_ there is less and less of a requirement to
> maintain IceTea, and that everything there can get moved over into the
> appropriate OpenJDK repo.  Not that I have anything against IceTea, it just
> would be nice to cut down on the amount of work needed to maintain all these
> separate codebases.

We agree.  Most of IcedTea is there by necessity, not design. See for our
progress on getting everything upstream where we can.

> --
> Erik Trimble
> Java System Support
> Mailstop:  usca22-123
> Phone:  x17195
> Santa Clara, CA
> Timezone: US/Pacific (GMT-0800)

Andrew :-)

Free Java Software Engineer
Red Hat, Inc. (

Support Free Java!
Contribute to GNU Classpath and the OpenJDK

PGP Key: 94EFD9D8 (
Fingerprint: F8EF F1EA 401E 2E60 15FA  7927 142C 2591 94EF D9D8

More information about the distro-pkg-dev mailing list