llvm dev - Nov 2015 - Unstable UBSan tests on AArch64

On 2 November 2015 at 18:40, Adhemerval Zanella
<adhemerval.zanella at linaro.org> wrote:
> Is it 39 or 42-bit VMA? I noted a 42-bit issue in segment definition
> that I have fixed on my TSAN unification mapping patch [1]:
No, that's 39-bit.

cheers,
--renato

Right, it could be a case where the thread stack is being places in below
0x7f00000000. On the TSAN unification patch I also lower the high memory
start from 0x7e00000000 to 0x7d00000000, which can give more VMA available.
Strange that I have not yet see any similar issue in my environment.

On 02-11-2015 16:57, Renato Golin wrote:
> On 2 November 2015 at 18:40, Adhemerval Zanella
> <adhemerval.zanella at linaro.org> wrote:
>> Is it 39 or 42-bit VMA? I noted a 42-bit issue in segment definition
>> that I have fixed on my TSAN unification mapping patch [1]:
> 
> No, that's 39-bit.
> 
> cheers,
> --renato
>

On 2 November 2015 at 19:11, Adhemerval Zanella
<adhemerval.zanella at linaro.org> wrote:
> Right, it could be a case where the thread stack is being places in below
> 0x7f00000000. On the TSAN unification patch I also lower the high memory
> start from 0x7e00000000 to 0x7d00000000, which can give more VMA available.
> Strange that I have not yet see any similar issue in my environment.
This was happening once every few builds. It could be that you never got it.

We may have to wait a few builds after the VMA unification to move the
bot back to active duty.

--renato