AArch64 in JDK 9?
aph at redhat.com
Tue Apr 22 09:41:53 UTC 2014
On 04/19/2014 08:23 PM, Vladimir Kozlov wrote:
> On 4/19/14 1:17 AM, Andrew Haley wrote:
>> On 04/17/2014 11:16 AM, Volker Simonis wrote:
>>> I'd highly welcome your port in the main HotSpot tree!
>>> Unfortunately I'm not the decision maker here, but I can try to
>>> outline the steps we took to bring in our port and cc some people
>>> (Iris, Azeem) who may know how to help.
>>> - First of all we were told to and finally filed a JEP for the
>>> integration project (in our case it was JEP 175: PowerPC/AIX Port -
>>> http://openjdk.java.net/jeps/175). I think the main reason why this is
>>> necessary is that such a project requires a certain amount of help
>>> from Oracle and in order to get that you'll need to get your project
>>> sponsored and funded. This all is formalized trough the JEP process.
> Yes, until JEP is funded we can do nothing from Oracle side. It
> could take time based on ppc-aix port experience.
>>> - You'll probably need to have a "staging" repository as a mirror of
>>> the current jdk9-dev forest. The staging repository will be kept in
>>> sync with its mirror and additionally collect all your porting changes
>>> as valid (i.e. in the sense of 'jcheck') and reviewed OpenJDK
>> Sure, I was planning to do that anyway. There is one thing I don't
>> understand how to do, though. jcheck wants bug IDs for all changes,
>> right? So does that mean that you have to create bug IDs when you
>> create the staging repository?
> Staging repository is created by cloning jdk9-dev forest. After that
> any changeset which will be pushed into that repo have to have a
> valid changeset descriptor/comment:
> You have to file a separate bug in JBS for each patch, preferable
> with "AArch64:" prefix in bug's subject. Here is what we had for
> first ppc64 changes:
> It also helped a lot with ppc-aix port when SAP prepared list of all
> patches they wanted to push so we could preview them and estimate
> needed efforts during JEP review:
> It was also important to break the port into separate small/medium patches for easy review and testing.
Right, I can now see a plan.
More information about the hotspot-dev