HotSpot 14

[Andrew Haley]

Erik Trimble wrote:
> 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?

> 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.
> 
> Now, that said, maybe It's Time Right Now.

Yes, it is.  It has been for some time.

> 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.
> 
> 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.

We're working on that.

> 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.

Sure, but from what I've seen many (most?) of the community patches to the VM
are changes that need to go upstream (i.e. to HSX) anyway.  Keeping them as
OpenJDK6-only makes little sense.

Andrew.