(original) (raw)

Hi David,

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.

Cheers,
Lang.

On Tue, Sep 11, 2018 at 12:14 PM David A. Greene <dag@cray.com> wrote:
Just a quick note to say that I saw this. I'm tracking down what looks
like another issue which may be undefined behavior within a PassManager
test. That's more critical for us at the moment so I'm going to
diagnose and send a report about that before getting back to the JIT
tests. In the meantime, if Lang knows anything, that would be helpful.

\-David


David Blaikie via llvm-dev <llvm-dev@lists.llvm.org> writes:

\> +lhames, JIT Ring Master
\>
\> David - do you have any further info on the failures? How are these
\> tests failing (what errors, crashes, etc? backtraces?)? Might get
\> something useful out of running them under a sanitizer or valgrind
\> (might not - not sure if all of their lower-level behavior is
\> understood/valid with those kinds of checkers)
\>
\> On Mon, Sep 10, 2018 at 8:18 PM David Greene via llvm-dev
\> <llvm-dev@lists.llvm.org> wrote:
\>
\> Hi all,
\>
\> I am seeing a number of JIT unit test failures on AArch64\. Some
\> googling returns
\> past discussions (circa 2014) but as far as I can tell, everything
\> should be working.
\> I listed the failures below.
\>
\> These are from a Release build. A Debug build does not exhibit the
\> failures. I built
\> with gcc 6.1.0 on SuSE 12\. Switching to gcc 8.2.0 also makes the
\> problem go away,
\> both in Debug and Release builds.
\>
\> Is there a known problem with gcc 6.1.0 on AArch64? I considered
\> the possiblity
\> that the tests (or libraries) somehow wander into undefined
\> behavior territory
\> but my guess is that's unlikely.
\>
\> -David
\>
\> \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
\> Testing: 0 .. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90..
\> Testing Time: 5.12s
\> \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
\> Failing Tests (11):
\> LLVM-Unit ::
\> ExecutionEngine/MCJIT/./MCJITTests/MCJITTest.lazy\_function\_creator\_
\> lambda
\> LLVM-Unit ::
\> ExecutionEngine/Orc/./OrcJITTests/CoreAPIsStandardTest.DefineMaterializingSymbol
\> LLVM-Unit ::
\> ExecutionEngine/Orc/./OrcJITTests/CoreAPIsStandardTest.FallbackDefinitionGeneratorTest
\> LLVM-Unit ::
\> ExecutionEngine/Orc/./OrcJITTests/DummyRPC.ReturnErrorFailure
\> LLVM-Unit ::
\> ExecutionEngine/Orc/./OrcJITTests/DummyRPC.ReturnExpectedFailure
\> LLVM-Unit ::
\> ExecutionEngine/Orc/./OrcJITTests/RemoteObjectLayer.AddObjectFailure
\> LLVM-Unit ::
\> ExecutionEngine/Orc/./OrcJITTests/RemoteObjectLayer.EmitAndFinalizeFailure
\> LLVM-Unit ::
\> ExecutionEngine/Orc/./OrcJITTests/RemoteObjectLayer.FindSymbol
\> LLVM-Unit ::
\> ExecutionEngine/Orc/./OrcJITTests/RemoteObjectLayer.FindSymbolIn
\> LLVM-Unit ::
\> ExecutionEngine/Orc/./OrcJITTests/RemoteObjectLayer.RemoveObjectFailure
\> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\> LLVM Developers mailing list
\> llvm-dev@lists.llvm.org
\> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
\>
\> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\> LLVM Developers mailing list
\> llvm-dev@lists.llvm.org
\> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev