HotSpot 14

Andrew John Hughes gnu_andrew at member.fsf.org
Fri May 29 05:06:39 PDT 2009


2009/5/29 David Cox <David.Cox at sun.com>:
> Hi,
>
> Erik Trimble wrote:
>>
>> Andrew John Hughes wrote:
>>>
>>> 2009/5/15 Erik Trimble <Erik.Trimble at sun.com>:
>>>
>>>>
>>>> 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.
>>>>
>>>> Now, that said, maybe It's Time Right Now.
>>>>
>>>>
>>>> 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.  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.
>>>>
>>>> --
>>>> Erik Trimble
>>>> Java System Support
>>>> Mailstop:  usca22-123
>>>> Phone:  x17195
>>>> Santa Clara, CA
>>>> Timezone: US/Pacific (GMT-0800)
>>>>
>>>>
>>>>
>>>
>>> I haven't seen any further movement on this; what's the progress on
>>> getting HotSpot updated/removed from OpenJDK6?
>>>
>>> It seems Sun just shipped a 6u14 release, and this included hs14b16.
>>> Strange then, that the new HotSpot Express repositories only have up
>>> to hs14b15.  Deja vu?
>>>
>>
>> I've been distracted with the JavaOne stuff and some internal work.
>>
>> I'll push the latest hs14b16 work (it's one patch) into the HSX14 repo
>> now.
>>
>> We still need to have a discussion again about where future (external)
>> work on HS14 goes, and if we want to push HSX14 to the Open6 repo now.
>
> After pushing the late-breaking fix to the Serviceability Agent in Sun's
> hs14-b16 to OpenJDK's hsx/hsx14, I think hsx14 should be merged into OpenJDK
> 6.
>
> If the HotSpot Express Project is to host the "tip" of open HotSpot
> development, then the changeset that was recently made to HotSpot make files
> in  OpenJDK 6
> (http://hg.openjdk.java.net/jdk6/jdk6/hotspot/rev/fc30e742f2fc) should also
> be applied to hsx/hsx14.  However, that presents a problem.  Sun is now
> supporting HotSpot 14.0 with our Java SE for Business product.  Given that
> Sun will create its own branches (builds) of HotSpot 14.n, how should the VM
> in hsx/hsx14 be identified?  What constitutes a build of hsx14?
>
> Dave
>

Porting that changeset to hsx and getting rid of a local OpenJDK6 copy
would seem the simplest solution long term.  There doesn't seem to be
an advantage in maintaining an OpenJDK6 copy.

I don't really follow your other comments.  I thought the intention
with HotSpot Express is that it would be the branch of HotSpot 14.n
that Sun ships.  That was the whole point from my perspective, so we
were all working on the same page.
-- 
Andrew :-)

Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

Support Free Java!
Contribute to GNU Classpath and the OpenJDK
http://www.gnu.org/software/classpath
http://openjdk.java.net

PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA  7927 142C 2591 94EF D9D8



More information about the jdk6-dev mailing list