OpenJDK rebuilding on windows takes a long time

[Kelly O'Hair]

On Feb 14, 2013, at 2:24 AM, Alexander Scherbatiy wrote:

> On 2/13/2013 8:45 PM, Kelly O'Hair wrote:
>> You are pointing at the fastdebug jdk as your boot jdk, why?
>> 
>> The official boot jdk for jdk8 is jdk7u7 we cannot guarantee anything else will work, although it should,
>> when tracking down issues like this, you need to narrow down all the possible differences.
>> 
>> I have no idea at this time what the 'sync state' is with the awt team forest.
>> My recommendation would be to clone the official jdk8/jdk8 forest, which can be assumed to work since
>> RE should have built it, or any integrator pushing changes into it should have built it.
>> Create 2 forests of so you can do separate experiments on each.
>    The question was about time rebuilding JDK after a small change.

And I asked, why are you pointing at a fastdebug JDK for your boot jdk?   --with-boot-jdk=/cygdrive/c/Sun/Tools/JDK/jdk7/7u14/b10/jdk1.7.0_14/fastdebug

Doesn't matter what the change is, if you use a debug JDK, it will be slow.

> 
>   What time does it take to rebuild the official  jdk8/jdk8 forest with default options after small change in the java file like javax.swing.JFrame ?

You have asked a question that cannot be answered without more data. It depends on dozens of things.
What the change is, what the machine is, how many CPUs, how much RAM, how fast is the disk, what else is running on the system,
what boot jdk you are using, etc etc.  And even if we have that data, the best measure is trying it yourself, everybody's
machine will be different.

>   Is sjavac are enabled by default now in the  official  jdk8/jdk8?  If no,  what time does it take to rebuild the JDK with the --enable-sjavac option?

sjavac is NOT on by default.

Once the langtools team gives us some indication it is ready for primetime, and would be ready to deal with any
urgent issues we might encounter, we can do our own experiments, insure RE is ok with the change, and then
change the default.  In the mean time, developers can turn it on themselves if they want to try it.

Again, you are asking "what time does it take" questions that are extremely hard to answer.
The expectation is that sjavac might benefit a complete JDK rebuild a little, but that the big benefit with sjavac
will be developers making just a few changes. But again, there are too many variables involved to give you
an absolute number.

-kto

> 
>   Thanks,
>   Alexandr.
> 
>> Then do the build from the root with a 7u7 jdk in your PATH (no need for the --with-boot-jdk option).
>> Do a build without --enable-sjavac on one forest, then with it on the other.
>> 
>> -kto
>> 
>> On Feb 13, 2013, at 3:38 AM, Alexander Scherbatiy wrote:
>> 
>>> On 2/11/2013 4:03 PM, Erik Joelsson wrote:
>>>> The long term solution to this is sjavac. I do not know if it has made it into that forest yet. You can try by adding --enable-sjavac to configure and do a clean build. If the build works, you have it, and incremental builds will be much faster.
>>>   I tried to use the --enable-sjavac option and JDK 7 and 8 as a boot JDK.
>>>      --with-boot-jdk=/cygdrive/c/Sun/Tools/JDK/jdk7/7u14/b10/jdk1.7.0_14/fastdebug --with-target-bits=32 --enable-sjavac
>>>       gives compilation error
>>> 
>>>    --with-boot-jdk=/cygdrive/c/Sun/Tools/JDK/jdk8/b75/jdk1.8.0/fastdebug --with-target-bits=32 --enable-sjavac
>>>      gives "OutOfMemoryError: Java heap space" error.
>>> 
>>>   The log files are attached.
>>> 
>>>   Thanks,
>>>   Alexandr.
>>> 
>>>> /Erik
>>>> 
>>>> On 2013-02-11 12:22, Alexander Scherbatiy wrote:
>>>>> On 2/8/2013 6:46 PM, Erik Joelsson wrote:
>>>>>> Ccache is not supported on windows since it doesn't work with visual studio AFAIK.
>>>>>> 
>>>>>> What kind of change did you do? Was it in native code or java and in which repository?
>>>>>  I use the http://hg.openjdk.java.net/jdk8/awt repository, edit java code and build the jdk.
>>>>> To reproduce the issue:
>>>>>  - open the javax.swing.JFrame class and add a comment line:
>>>>>    // a comment
>>>>>  - build jdk
>>>>> 
>>>>> ----- Build times -------
>>>>> Start 2013-02-11 15:09:55
>>>>> End   2013-02-11 15:17:08
>>>>> 00:00:03 corba
>>>>> 00:00:02 hotspot
>>>>> 00:00:01 jaxp
>>>>> 00:00:03 jaxws
>>>>> 00:06:54 jdk
>>>>> 00:00:02 langtools
>>>>> 00:07:13 TOTAL
>>>>> -------------------------
>>>>> 
>>>>> My environment:
>>>>>  OS: Windows 7 Professional, x64
>>>>>  Processor - Intel Core i7
>>>>>  Memory - 8 GB
>>>>> 
>>>>> The log file is attached.
>>>>> 
>>>>> Thanks,
>>>>> Alexandr.
>>>>>> /Erik
>>>>>> 
>>> 
>>> <jdk7_log.txt><jkd8_log.txt>
>