[LLVMbugs] [Bug 531] NEW: when bugpointing the attached bytecode the CBE crashes

bugzilla-daemon at cs.uiuc.edu bugzilla-daemon at cs.uiuc.edu
Sun Feb 27 12:21:10 PST 2005


           Summary: when bugpointing the attached bytecode the CBE crashes
           Product: tools
           Version: trunk
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: bugpoint
        AssignedTo: unassignedbugs at nondot.org
        ReportedBy: alkis at cs.uiuc.edu

Here is the output when running bugpoint on the attached bytecode using 
gccld's optimizations: 
Read input file      : 'Output/heapsort.raw.llvm.bc' 
*** All input ok 
Running selected passes on program to test for crash: Success! 
Found gcc: /usr/lib/ccache/bin/gcc 
Initializing execution environment: Running the code generator to test for a 
crash: <cbe> 
Generating reference output from raw program: <cbe><gcc><program>Reference 
output is: bugpoint.reference.out-9S66f5 
*** Checking the code generator... 
*** Debugging miscompilation! 
Checking to see if '' compile correctly: <cbe><gcc><program> yup. 
Checking to see if '-funcresolve -internalize -globalopt -constmerge -ipsccp 
-deadargelim -inline -prune-eh -globalopt -globaldce -argpromotion 
-instcombine -scalarrepl -globalsmodref-aa -loopsimplify -licm -load-vn -gcse 
-dse -instcombine -simplifycfg -globaldce -verify' compile correctly: <cbe> 
Error running tool: 
  /home/alkis/projects/college/2llvm/Debug/bin/llc -o 
bugpoint-output.bc-AjJj0e.cbe.c -march=c -f bugpoint-output.bc-AjJj0e 
*** Debugging code generator crash! 
Checking to see if we can delete global inits: <cbe> 
  - Removing all global inits hides problem! 
After bugpoint generates the reference output, it optimizes the input 
bytecode. Compiling that with the CBE fails (whereas llc doesn't). Apparently 
the CBE enters an infinite loop inside CWriter::printType while trying to 
print JNIEnv.

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