[LLVMbugs] [Bug 1544] NEW: Bugpoint failed to reduce the bitcode

bugzilla-daemon at cs.uiuc.edu bugzilla-daemon at cs.uiuc.edu
Mon Jul 9 00:06:46 PDT 2007


http://llvm.org/bugs/show_bug.cgi?id=1544

           Summary: Bugpoint failed to reduce the bitcode
           Product: tools
           Version: trunk
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: bugpoint
        AssignedTo: unassignedbugs at nondot.org
        ReportedBy: asl at math.spbu.ru


Consider the attached bitcode.

Running
./bugpoint -run-llc nsPrintEngine.bc -tool-args -mcpu=athlon -relocation-model=pic
results:

Read input file      : 'nsPrintEngine.bc'
*** All input ok
Found gcc: /usr/bin/gcc
Initializing execution environment: Running the code generator to test for a
crash: <llc>
Error running tool:
  ./llc -mcpu=athlon -relocation-model=pic -o
bugpoint-test-program.bc-H78I0s.llc.s -f bugpoint-test-program.bc-H78I0s
llc: /home/asl/proj/llvm/src/lib/Target/X86/X86FloatingPoint.cpp:768: void
<unnamed>::FPS::handleTwoArgFP(llvm::ilist_iterator<llvm::MachineInstr>&):
Assertion `UpdatedSlot < StackTop && Dest < 7' failed.
./llc((anonymous namespace)::PrintStackTrace()+0x1f)[0x86ca4bf]
/lib/libc.so.6(abort+0xec)[0xb7ca6c0c]
/lib/libc.so.6(__assert_fail+0xeb)[0xb7c9e95b]
./llc((anonymous
namespace)::FPS::handleTwoArgFP(llvm::ilist_iterator<llvm::MachineInstr>&)+0xd49)[0x82d0069]
*** Debugging code generator crash!


bugpoint: /home/asl/proj/llvm/src/lib/Bitcode/Writer/ValueEnumerator.h:68:
unsigned int llvm::ValueEnumerator::getValueID(const llvm::Value*) const:
Assertion `I != ValueMap.end() && "Value not in slotcalculator!"' failed.
Checking to see if we can delete global inits: ./bugpoint((anonymous
namespace)::PrintStackTrace()+0x1f)[0x83f898f]
/lib/libc.so.6(abort+0xec)[0xb7d87c0c]
/lib/libc.so.6(__assert_fail+0xeb)[0xb7d7f95b]
./bugpoint[0x81436ca]

Is bugpoint broken? Or, maybe some bitcode writing machinery?



------- 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