[LLVMbugs] [Bug 877] NEW: core dump by -condprop optimization pass
bugzilla-daemon at cs.uiuc.edu
bugzilla-daemon at cs.uiuc.edu
Fri Aug 11 17:13:56 PDT 2006
http://llvm.org/bugs/show_bug.cgi?id=877
Summary: core dump by -condprop optimization pass
Product: tools
Version: trunk
Platform: Macintosh
OS/Version: MacOS X
Status: NEW
Severity: normal
Priority: P2
Component: opt
AssignedTo: unassignedbugs at nondot.org
ReportedBy: pjenkins at apple.com
CC: pjenkins at apple.com
Running `opt bugpoint-reduced-condprop.8-11-2006.bc -condprop` produces the
following output:
WARNING: You're attempting to print out a bytecode file.
This is inadvisable as it may cause display problems. If
you REALLY want to taste LLVM bytecode first-hand, you
can force output with the `-f' option.
PHINode should have one entry for each predecessor of its parent basic block!
%tmp.i119.lcssa35.lcssa.lcssa.lcssa.lcssa.lcssa = phi
"struct.kc::impl_elem_patternrepresentation"* [ null, %bb1077 ] ;
<"struct.kc::impl_elem_patternrepresentation"*> [#uses=0]
Broken module found, compilation aborted!
Abort trap
The bytecode file can be found at:
http://www.patjenk.com/llvm/bugpoint-reduced-condprop.8-11-2006.bc
This error first occurred on a dual g5 running a beta version of mac os 10.5 and
was reproduced on a g4 running mac os 10.4.6. I was using the latest llvm CVS on
both machines.
The bug was exposed by running the following passes through bugpoint on kimwitu++:
-simplifycfg -instcombine -loopsimplify -instcombine -inline -sccp -lowersetjmp
-reassociate -adce -scalarrepl -loop-unswitch -condprop -mergereturn
-raiseallocs -dse -instcombine -tailcallelim -funcresolve -lcssa -mem2reg
-constmerge -simplifycfg -condprop -prune-eh -simplifycfg -argpromotion -basiccg
-globalopt -simplifycfg -verify -licm -instcombine -raise -verify -simplifycfg
-deadtypeelim -gcse -basiccg -break-crit-edges -loop-unroll -tailduplicate
-ipconstprop -deadargelim -simplify-libcalls -globaldce -instcombine -load-vn
-break-crit-edges -indvars
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the llvm-bugs
mailing list