[LLVMbugs] [Bug 5235] New: llc: Assertion `HasInsideLoopSuccs && " Loop block has no in-loop successors!"' failed.
bugzilla-daemon at cs.uiuc.edu
bugzilla-daemon at cs.uiuc.edu
Sun Oct 18 13:36:25 PDT 2009
http://llvm.org/bugs/show_bug.cgi?id=5235
Summary: llc: Assertion `HasInsideLoopSuccs && "Loop block has no
in-loop successors!"' failed.
Product: new-bugs
Version: trunk
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: new bugs
AssignedTo: unassignedbugs at nondot.org
ReportedBy: edwintorok at gmail.com
CC: llvmbugs at cs.uiuc.edu
Attempting to codegen an -O0 compiled file with llc fails:
/home/edwin/llvm-git/obj/Release/bin/llc bugpoint-reduced-simplified.bc
llc: /home/edwin/llvm-git/llvm/include/llvm/Analysis/LoopInfo.h:426: void
llvm::LoopBase<N, M>::verifyLoop() const [with BlockT = llvm::BasicBlock, LoopT
= llvm::Loop]: Assertion `HasInsideLoopSuccs && "Loop block has no in-loop
successors!"' failed.
0 llc 0x0000000000f3b5ff
1 llc 0x0000000000f3d2c9
2 libpthread.so.0 0x0000003411e0e720
3 libc.so.6 0x0000003411231d25 gsignal + 53
4 libc.so.6 0x0000003411234de1 abort + 385
5 libc.so.6 0x000000341122af99 __assert_fail + 233
6 llc 0x0000000000df871c llvm::LoopBase<llvm::BasicBlock,
llvm::Loop>::verifyLoop() const + 2700
7 llc 0x0000000000dfb54b
llvm::LPPassManager::runOnFunction(llvm::Function&) + 1659
8 llc 0x0000000000ec95a1
llvm::FPPassManager::runOnFunction(llvm::Function&) + 561
9 llc 0x0000000000ec97b6
llvm::FunctionPassManagerImpl::run(llvm::Function&) + 166
10 llc 0x0000000000ec9a25
llvm::FunctionPassManager::run(llvm::Function&) + 85
11 llc 0x000000000054b614 main + 6452
12 libc.so.6 0x000000341121e5c6 __libc_start_main + 230
13 llc 0x0000000000549179
Stack dump:
0. Program arguments: /home/edwin/llvm-git/obj/Release/bin/llc
bugpoint-reduced-simplified.bc
1. Running pass 'Loop Pass Manager' on function '@is_extract_cab'
Aborted
If I run -simplifycfg and then run llc it works.
--
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the llvm-bugs
mailing list