https://llvm.org/bugs/show_bug.cgi?id=26882
Bug ID: 26882
Summary: Compiler flags' combination leads to segfault
Product: libraries
Version: 3.8
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Backend: ARM
Assignee: unassignedb...@nondot.org
Reporter: tulip...@gmail.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified
It seems explicit cpu and interleave values don't go too well together.
$ rustc -O -C target-cpu=cortex-a5 -C
llvm-args=-force-target-max-vector-interleave=0 main.rs
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb2eb52a0 (LWP 28076)]
0xb3576404 in llvm::IRBuilder<true, llvm::ConstantFolder,
llvm::IRBuilderDefaultInserter<true> >::CreateExtractElement(llvm::Value*,
llvm::Value*, llvm::Twine const&) ()
from /home/odroid/rust-nightly-sysalloc/bin/../lib/librustc_llvm-9026086f.so
(gdb) bt
#0 0xb3576404 in llvm::IRBuilder<true, llvm::ConstantFolder,
llvm::IRBuilderDefaultInserter<true> >::CreateExtractElement(llvm::Value*,
llvm::Value*, llvm::Twine const&) ()
from /home/odroid/rust-nightly-sysalloc/bin/../lib/librustc_llvm-9026086f.so
#1 0xb3585c14 in (anonymous
namespace)::InnerLoopVectorizer::vectorizeMemoryInstruction(llvm::Instruction*)
() from /home/odroid/rust-nightly-sysalloc/bin/../lib/librustc_llvm-9026086f.so
#2 0xb3583dfc in (anonymous
namespace)::InnerLoopVectorizer::vectorizeBlockInLoop(llvm::BasicBlock*,
llvm::SmallVector<llvm::PHINode*, 4u>*) ()
from /home/odroid/rust-nightly-sysalloc/bin/../lib/librustc_llvm-9026086f.so
#3 0xb35889a8 in (anonymous namespace)::InnerLoopVectorizer::vectorizeLoop()
()
from /home/odroid/rust-nightly-sysalloc/bin/../lib/librustc_llvm-9026086f.so
#4 0xb358c7c8 in (anonymous
namespace)::LoopVectorize::processLoop(llvm::Loop*) ()
from /home/odroid/rust-nightly-sysalloc/bin/../lib/librustc_llvm-9026086f.so
#5 0xaf904680 in ?? ()
Not using an explicit -mcpu doesn't lead to the crash even with
`force-target-max-vector-interleave` set to zero. While that particular value
might not make much sense it should be handled more gracefully :)
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
