jdk9 builds status

[Andrey Petushkov]

Dear Alex,

pardon for the delayed response. Actually we've reworked the the code which
exhibits this problem, because we've found it's not robust vs different
toolchains and compilation options. So finally we're using pure assembler
to obtain the value of the stack pointer. We'll soon publish the respective
changeset

Regards,
Andrey

On Wed, May 25, 2016 at 5:41 PM Alex Kashchenko <akashche at redhat.com> wrote:

> Hi,
>
> I found that jdk9 in http://hg.openjdk.java.net/aarch32-port/jdk9/ is
> broken after the "pre C1" commit due to this discrepancy:
>
>   - jdk8u:
>
> http://hg.openjdk.java.net/aarch32-port/jdk8u/hotspot/rev/b3e996878ddf#l35.6
>   - jdk9:
> http://hg.openjdk.java.net/aarch32-port/jdk9/hotspot/rev/52d292d5c12f#l35.7
>
> "fp" register is zero at that point and vm crashes on startup.
>
> With the following change:
>
>   address os::current_stack_pointer()  {
> -  register void* fp __asm__ (SPELL_REG_FP);
> +  register void* sp __asm__ (SPELL_REG_SP);
>     // Only lr on top of fp
> -  return (address) fp + BytesPerWord;
> +  return (address) sp;
>   }
>
> jdk9 works and can bootstrap itself - I've built slowdebug jdk9 using a
> fastdebug one as a boot jdk.
>
> This is just a "heads up" - I am not proposing to integrate this change,
> as it differs from jdk8u and initial change in that place (linked above)
> probably has been done for the reason.
>
> PS: additional question on aarch32-jdk9 plans: as upstream jdk9 is
> feature complete now, does it make sense to update aarch32-jdk9 forest
> from it or is it better to wait for some point closer to jdk9 release?
>
> --
> -Alex
>