[LLVMbugs] [Bug 7154] New: Nightly test failures for -O0 -g

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Mon May 17 12:49:54 PDT 2010


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

           Summary: Nightly test failures for -O0 -g
           Product: libraries
           Version: trunk
          Platform: Macintosh
        OS/Version: MacOS X
            Status: NEW
          Severity: normal
          Priority: P
         Component: Register Allocator
        AssignedTo: unassignedbugs at nondot.org
        ReportedBy: stoklund at 2pi.dk
                CC: llvmbugs at cs.uiuc.edu


I ran the nightly test suite on x86_64-darwin in a debug build with
-regalloc=local and -regalloc=fast.

There were failures:

Fast allocator failures:
$ make TEST=nightly OPTFLAGS=-O0 EXTRA_OPTIONS=-g PIC_CODEGEN=1 DISABLE_LTO=1
LLCFLAGS='-O0 -relocation-model=pic -disable-fp-elim -regalloc=fast'
ENABLE_PARALLEL_REPORT=1 DISABLE_CBE=1 DISABLE_JIT=1 report -j10

External/SPEC/CFP2006/447.dealII/447.dealII
External/SPEC/CINT2000/176.gcc/176.gcc     
External/SPEC/CINT2006/403.gcc/403.gcc     
MultiSource/Applications/JM/ldecod/ldecod  
MultiSource/Applications/JM/lencod/lencod  
MultiSource/Applications/aha/aha           

Local allocator failures:
$ make TEST=nightly OPTFLAGS=-O0 EXTRA_OPTIONS=-g PIC_CODEGEN=1 DISABLE_LTO=1
LLCFLAGS='-O0 -relocation-model=pic -disable-fp-elim -regalloc=local'
ENABLE_PARALLEL_REPORT=1 DISABLE_CBE=1 DISABLE_JIT=1 report -j10

External/SPEC/CFP2006/447.dealII/447.dealII                             
External/SPEC/CINT2000/176.gcc/176.gcc                                  
External/SPEC/CINT2006/403.gcc/403.gcc                                  
MultiSource/Applications/aha/aha                                        

Bugpoint isolates the vararg function gen_rtx() in the two gcc tests. It is
interesting that the two register allocators miscompile the same tests. Does
linear scan have secrets?

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