sharing graal experiments

[Christian Thalinger]

On Feb 20, 2013, at 5:48 PM, John Rose <john.r.rose at oracle.com> wrote:

> On Feb 18, 2013, at 7:30 PM, John Rose <john.r.rose at oracle.com> wrote:
> 
>> One more thought:  How about if we have graal/graal copied into sumatra-dev/graal, keeping the existing copy of jdk8/hotspot also.
>> 
>> Upside:  There will always be a known-good snapshot of the whole jdk8/* forest, and builds will be known to work modulo local changes (whether on branches or not).
>> 
>> For graal-based experiments we would expect developers to remove the "stock" hotspot and replace it with graal (mv hotspot{,-jdk8}; mv graal hotspot).
>> 
>> Downsides: Redundancy (although the hotspot and graal repos would be near duplicates).  Uncertainty as to where to host branches (stock hotspot vs. graal).
> 
> Having slept on this idea, I like it.  We'll have a "matched set" of jdk8, plus graal.  We'll need a custom build procedure that will take the hotspot sources from graal instead of the standard jdk8/hotspot.
> 
> http://hg.openjdk.java.net/sumatra/sumatra-dev/{jdk,hotspot,...}
> http://hg.openjdk.java.net/sumatra/sumatra-dev/graal
> http://hg.openjdk.java.net/sumatra/sumatra-dev/scratch
> 
> Any objections to making the graal repo this way?

Not an objection but the graal repository should always be able to build stock hotspot.  So when we pull the whole jdk8 forest we also get the latest hotspot changes into sumatra-dev/hotspot (which is a clone of graal/graal).

-- Chris

> 
> — John