[llvm-dev] JIT tests on AArch64

[Lang Hames via llvm-dev]

Ok.

I am not aware of any specific issues with gcc 6.1.0, but for what it's
worth ORC code is heavy on lambdas, std::function, and promises/futures
compared to the rest of LLVM. In the past it has ICE'd a few GCC versions
(workarounds have been made in tree for this) and shown up bugs in MSVC's
standard library implementation. Bug reports for those features are the
first place I look now when I see a failing builder running an older GCC
fail while the rest of the builders are green.

Cheers,
Lang.



On Sat, Sep 22, 2018 at 4:07 PM David Greene <dag at cray.com> wrote:

> Other general LLVM tests fail with 8.2.0.
>
> Don't spend too much time chasing this down.  I just wanted to see if
> anyone is aware of issues with gcc 6.1.0.  Sounds like not.  I will keep
> investigating on our end.  It may be something with our environment is
> strange.  If/when I figure something out I'll report it.
>
>                                          -David
>
> ________________________________________
> From: Lang Hames <lhames at gmail.com>
> Sent: Friday, September 21, 2018 5:03:39 PM
> To: David Greene
> Cc: LLVM Developers Mailing List
> Subject: Re: [llvm-dev] JIT tests on AArch64
>
> Hi David,
>
> I don't have access to a gcc 6.1.0 / aarch64 setup, but I've tried the
> tests locally and they're passing asan/ubsan/tsan clean, and there is no
> obvious uninitialized memory use in the test case (though who knows where
> it might be inlined from in a release build).
>
> When you say other tests broke with 8.2.0, do you mean other ORC tests
> specifically, or just other LLVM tests?
>
> Cheers,
> Lang.
>
> On Tue, Sep 18, 2018 at 8:07 AM David Greene <dag at cray.com<mailto:
> dag at cray.com>> wrote:
> "David A. Greene via llvm-dev" <llvm-dev at lists.llvm.org<mailto:
> llvm-dev at lists.llvm.org>> writes:
>
> > Lang Hames via llvm-dev <llvm-dev at lists.llvm.org<mailto:
> llvm-dev at lists.llvm.org>> writes:
> >
> >> I am afraid nothing leaps to mind. Once you have a chance to look at
> >> them again please let me know -- I'd be happy to look at backtraces /
> >> failures.
> >
> > Huh.  Now the problem has disappeared.  A colleague updated to ToT and
> > now I'm not seeing the failures, even with gcc 6.1.0 in Release mode.
>
> User error.  I was building on the wrong branch!
>
> I am still seeing these errors with gcc 6.1.0 in Release mode.
>
> Is there anything else useful I can provide to help track this down?
>
> When I tried gcc 8.2.0 these tests passed but some others broke.  :(
>
>                          -David
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180924/6ac6b202/attachment.html>