bootcycle build on ix86-linux-gnu broken since jdk-13+18

[Ioi Lam]

Matthias,

Could you send the exact steps for reproducing this? Are you doing 
something like this?

    cd openjdk13src
    mkdir build
    cd build
    bash ../configure -- --with-target-bits=32
    make bootcycle-images

Thanks
- Ioi


On 6/17/19 2:35 AM, Matthias Klose wrote:
> On 17.06.19 09:45, David Holmes wrote:
>> <dropped jdk-dev>
>>
>> < cc'ing Calvin>
>>
>> Hi Matthias,
>>
>> This looks like an issue with the new Dynamic Archive support. I'm not sure if
>> it is intended for use on 32-bit, but it looks like the size of the file to map
>> is too large. (or it may relate to the issue Aleksey pointed too - either way it
>> starts from dynamic archive code.)
> yes, configuring with --disable-cds works around the build failure.  Looking at
> the other 32bit hotspot build, it looks like the armhf build works with enabled cds.
>
> Matthias
>
>> Cheers,
>> David
>>
>>
>>
>> On 15/06/2019 12:02 am, Matthias Klose wrote:
>>> On 14.06.19 15:10, David Holmes wrote:
>>>> Hi Matthias,
>>>>
>>>> On 14/06/2019 10:57 pm, Matthias Klose wrote:
>>>>> My last successful bootcycle build on i686-linux-gnu was jdk-13+18. After
>>>>> that I
>>>>> tried jdk-13+22, which didn't build anymore, with no change to the most recent
>>>>> jdk-13+25, and also seen in jdk-14+1.
>>>>>
>>>>> All builds fail with
>>>>>
>>>>> Compiling 12 properties into resource bundles for jdk.jdeps
>>>>> #
>>>>> # There is insufficient memory for the Java Runtime Environment to continue.
>>>>> # Native memory allocation (malloc) failed to allocate 2155274940 bytes for
>>>>> AllocateHeap
>>>>> # An error report file with more information is saved as:
>>>> Do you have the full stack for that? It might shed some light.
>>> now attached.
>>>