Peter Jones from Red Hat (pjo...@redhat.com ) seems to working on adding
support for aarch64, by the last common on the thread. His work seems
to be quite recent (6th may), so we might want to check with him if he
is planning to finish this work.
Another option might to check lld, we have it work
Thanks for telling us, however I think this is just an unusual test
situation not a bot error.
In https://lab.llvm.org/buildbot/#/builders/171/builds/118 Joel E.
Denny fixed the test so your guess is correct.
Looking at the fix
https://reviews.llvm.org/rGcc60fa2685bdbff889df826a1bfd5e52ffd163c8,
Hi Steve,
Thanks for the ping on this.
Adhemerval, Oliver, are either of you familiar with this stuff
https://sourceware.org/bugzilla/show_bug.cgi?id=26206 ?
Regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On 25 Jun 2021, at 15:13, Steve McIntyre <93...@debian.org> wrote:
>
> Hi folks,
>
Hi Philip,
I’m looking at logs of
https://lab.llvm.org/buildbot/#/builders/171/builds/112
and
https://lab.llvm.org/buildbot/#/builders/171/builds/113
— and I can’t spot anything wrong in buildbot commands.
I don’t have an explanation for this artefact.
Regards,
--
Maxim Kuvyrkov
https://www.li
This bot failure appears to be unrelated to the fingered change. From
the commit log, I'd guess that 9eaf0d120 by Joel E. Denny
was the triggering change, but that's not in the
blame list.
Joel, FYI.
Linaro folks, as bot owner, you should investigate why the blame list is
wrong. JFYI, this
I’m running historical performance experiments, and this commit from 2019
showed up on my radar. Just in case someone is interested in running Fortran
code on memory-constrained M-profile cores ...
It appears that Janne’s patch increases code-size of 437.leslie3d by around 2%
on 32-bit ARM (we
