http://llvm.org/bugs/show_bug.cgi?id=16255
Bug ID: 16255
Summary: llvm-aarch64-linux buildbot unit test failures
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Interprocedural Optimizations
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Classification: Unclassified
The http://lab.llvm.org:8011/builders/llvm-aarch64-linux buildbot has been set
up recently. This buildbot cross-compiles clang with itself, targeting
aarch64-linux, and then runs the LLVM regression tests with the resulting
binary in an aarch64-linux model.
The following regression tests fail, highlighting that there's an incorrect
code generation when clang/llvm compiles itself targeting AArch64 linux:
LLVM-Unit :: ADT/Release+Asserts/ADTTests/SmallVectorTest/0.InsertRangeTest
LLVM-Unit ::
ADT/Release+Asserts/ADTTests/SmallVectorTest/0.InsertRepeatedTest
LLVM-Unit :: ADT/Release+Asserts/ADTTests/SmallVectorTest/1.InsertRangeTest
LLVM-Unit ::
ADT/Release+Asserts/ADTTests/SmallVectorTest/1.InsertRepeatedTest
LLVM-Unit :: ADT/Release+Asserts/ADTTests/SmallVectorTest/2.InsertRangeTest
LLVM-Unit ::
ADT/Release+Asserts/ADTTests/SmallVectorTest/2.InsertRepeatedTest
LLVM-Unit :: ADT/Release+Asserts/ADTTests/SmallVectorTest/3.InsertRangeTest
LLVM-Unit ::
ADT/Release+Asserts/ADTTests/SmallVectorTest/3.InsertRepeatedTest
LLVM-Unit ::
Support/Release+Asserts/SupportTests/AllocationTests/MappedMemoryTest.AllocAndRelease/3
LLVM-Unit ::
Support/Release+Asserts/SupportTests/AllocationTests/MappedMemoryTest.AllocAndRelease/4
LLVM-Unit ::
Support/Release+Asserts/SupportTests/AllocationTests/MappedMemoryTest.DuplicateNear/3
LLVM-Unit ::
Support/Release+Asserts/SupportTests/AllocationTests/MappedMemoryTest.DuplicateNear/4
LLVM-Unit ::
Support/Release+Asserts/SupportTests/AllocationTests/MappedMemoryTest.EnabledWrite/3
LLVM-Unit ::
Support/Release+Asserts/SupportTests/AllocationTests/MappedMemoryTest.EnabledWrite/4
LLVM-Unit ::
Support/Release+Asserts/SupportTests/AllocationTests/MappedMemoryTest.MultipleAllocAndRelease/3
LLVM-Unit ::
Support/Release+Asserts/SupportTests/AllocationTests/MappedMemoryTest.MultipleAllocAndRelease/4
LLVM-Unit ::
Support/Release+Asserts/SupportTests/AllocationTests/MappedMemoryTest.SuccessiveNear/3
LLVM-Unit ::
Support/Release+Asserts/SupportTests/AllocationTests/MappedMemoryTest.SuccessiveNear/4
LLVM-Unit ::
Support/Release+Asserts/SupportTests/AllocationTests/MappedMemoryTest.UnalignedNear/3
LLVM-Unit ::
Support/Release+Asserts/SupportTests/AllocationTests/MappedMemoryTest.UnalignedNear/4
LLVM-Unit ::
Support/Release+Asserts/SupportTests/AllocationTests/MappedMemoryTest.ZeroNear/3
LLVM-Unit ::
Support/Release+Asserts/SupportTests/AllocationTests/MappedMemoryTest.ZeroNear/4
LLVM-Unit ::
Support/Release+Asserts/SupportTests/AllocationTests/MappedMemoryTest.ZeroSizeNear/3
LLVM-Unit ::
Support/Release+Asserts/SupportTests/AllocationTests/MappedMemoryTest.ZeroSizeNear/4
These test failures are probably caused by the DeadArgumentElimination pass
removing function arguments,
resulting in changes in how the AArch64 backend decides which arguments should
go in registers and which
ones should go on the stack.
Since there doesn't seem to be a backend:AArch64 component in bugzilla (yet),
I'm setting the component
to where DeadArgumentElimination lives: IPO.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
LLVMbugs mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs
