On 17 May 2017 at 18:07, John Brawn wrote:
> I've now tracked this down to a problem with LEApcrel rematerialization
> where the rematerialized LEApcrel can address a different literal pool
> to the original. I've raised https://bugs.llvm.org/show_bug.cgi?id=33074
Sounds nasty!
> This is actual
: 16 May 2017 19:13
> To: John Brawn
> Cc: James Molloy; Diana Picus; LLVM Commits; Clang Commits; nd
> Subject: Re: Potential self-hosting failure
>
> On 16 May 2017 at 18:26, John Brawn wrote:
> > I've managed to reproduce this, but no luck so far in figuring out
> >
On 16 May 2017 at 18:26, John Brawn wrote:
> I've managed to reproduce this, but no luck so far in figuring out
> what exactly is going wrong. I'll continue looking into it tomorrow.
Thanks John,
I have reverted it for now on r303193, to get the bots green.
cheers,
--renato
; Cc: James Molloy; Diana Picus; LLVM Commits; Clang Commits
> Subject: Potential self-hosting failure
>
> Hi John,
>
> It seems the LEApcrel patches have broken our self-hosting:
>
> http://lab.llvm.org:8011/builders/clang-cmake-thumbv7-a15-full-
> sh/builds/1550
>
>
Hi John,
It seems the LEApcrel patches have broken our self-hosting:
http://lab.llvm.org:8011/builders/clang-cmake-thumbv7-a15-full-sh/builds/1550
http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15-selfhost-neon/builds/1349
http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15-selfhost/b
