[llvm-testresults] buildbot failure in lab.llvm.org on phase1 - sanity

[Adrian Prantl]

Hi David,

I think this is your change. Do you need any help reproducing this? Looks like the error is Darwin-specific.

-- adrian


> On Aug 6, 2014, at 12:35 PM, llvmlab-buildmaster at lab.llvm.org wrote:
> 
> The Buildbot has detected a new failure on builder phase1 - sanity while building llvm.
> Full details are available at:
> http://lab.llvm.org:8013/builders/phase1%20-%20sanity/builds/3290
> 
> Buildbot URL: http://lab.llvm.org:8013/
> 
> Buildslave for this Build: macpro1
> 
> Build Reason: scheduler
> Build Source Stamp: 214988
> Blamelist: adrian,dblaikie,echristo
> 
> BUILD FAILED: failed
> 
> sincerely,
> -The Buildbot
> 
> 
> ================================================================================
> 
> CHANGES:
> File: test/DebugInfo/cu-line-tables.ll
> On: http://10.1.1.2/svn/llvm-project
> For: llvm
> At: Wed 06 Aug 2014 11:35:39
> Changed By: dblaikie
> Comments: DebugInfo: Fix ranges+gmlt test case to actually exercise the gmlt situation.
> 
> Originally this test case tested the specified behavior (that -gmlt
> would not produce DW_AT_ranges and that when no CU DW_AT_ranges were
> produced, no debug_ranges section (not even an empty list) would be
> produced) but then the ranges emission code was improved not to create
> ranges of a single element (instead favoring high_pc/low_pc) and so this
> test case no longer exercised the -gmlt portion of the behavior.
> 
> This caused me some confusion when reading the comments and trying to
> update this test case for future changes to -gmlt. I've made this test
> resilient to those changes (by using the {{DW_TAG|NULL}} pattern to
> block the end of the attribute search at the end of the CU's attribute
> list without mandating that it must (or must not) be followed by another
> tag (the future changes to -gmlt should produce no subprograms in this
> CU))
> 
> Fix the test case to have two functions in distinct sections to force
> the use of DW_AT_ranges.Properties: 
> 
> 
> 
> 
> File: lib/CodeGen/AsmPrinter/DbgValueHistoryCalculator.cpp
> On: http://10.1.1.2/svn/llvm-project
> For: llvm
> At: Wed 06 Aug 2014 11:55:39
> Changed By: adrian
> Comments: Cleanup collectChangingRegs
> 
> The handling of the epilogue is best expressed as an early exit and
> there is no reason to look for register defs in DbgValue MIs.
> 
> Patch by Frederic Riss!Properties: 
> 
> 
> 
> 
> File: lib/CodeGen/AsmPrinter/DbgValueHistoryCalculator.cpp
> On: http://10.1.1.2/svn/llvm-project
> For: llvm
> At: Wed 06 Aug 2014 11:55:39
> Changed By: adrian
> Comments: Improve performance of calculateDbgValueHistory.
> 
> In r210492 the logic of calculateDbgValueHistory was changed to end
> register variable live ranges at the end of MBB conditionally on
> the fact that the register was or not clobbered by the function body.
> 
> This requires an initial scan of all the operands of the function
> to collect all clobbered registers. In a second pass over all
> instructions, we compare this set with the set of clobbered
> registers for the current MachineInstruction. This modification
> incurred a compilation time regression on some benchmarks: the
> debug info emission phase takes ~10% more time.
> 
> While a small performance hit is unavoidable due to the initial
> scan requirement, we can improve the situation by avoiding to
> create too many temporary sets and just use lambdas to work directly
> on the result of the initial scan.
> 
> Fixes <rdar://problem/17884104>
> 
> Patch by Frederic Riss!Properties: 
> 
> 
> 
> 
> Files:
> include/llvm/CodeGen/CallingConvLower.h
> lib/CodeGen/CallingConvLower.cpp
> lib/Target/AArch64/AArch64CallingConvention.td
> lib/Target/AArch64/AArch64FastISel.cpp
> lib/Target/AArch64/AArch64ISelLowering.cpp
> lib/Target/ARM/ARMFastISel.cpp
> lib/Target/ARM/ARMISelLowering.cpp
> lib/Target/Hexagon/HexagonISelLowering.cpp
> lib/Target/MSP430/MSP430ISelLowering.cpp
> lib/Target/Mips/MipsCallingConv.td
> lib/Target/Mips/MipsISelLowering.cpp
> lib/Target/PowerPC/PPCCallingConv.td
> lib/Target/PowerPC/PPCFastISel.cpp
> lib/Target/PowerPC/PPCISelLowering.cpp
> lib/Target/R600/AMDGPUCallingConv.td
> lib/Target/R600/R600ISelLowering.cpp
> lib/Target/R600/SIISelLowering.cpp
> lib/Target/Sparc/SparcISelLowering.cpp
> lib/Target/SystemZ/SystemZISelLowering.cpp
> lib/Target/X86/X86CallingConv.td
> lib/Target/X86/X86FastISel.cpp
> lib/Target/X86/X86ISelLowering.cpp
> lib/Target/XCore/XCoreISelLowering.cpp
> utils/TableGen/CallingConvEmitter.cpp
> On: http://10.1.1.2/svn/llvm-project
> For: llvm
> At: Wed 06 Aug 2014 11:55:39
> Changed By: echristo
> Comments: Remove the target machine from CCState. Previously it was only used
> to get the subtarget and that's accessible from the MachineFunction
> now. This helps clear the way for smaller changes where we getting
> a subtarget will require passing in a MachineFunction/Function as
> well.Properties: 
> 
> 
> 
> 
> LOGS:
> 
>