[llvm-testresults] buildbot failure in lab.llvm.org on phase2 - living

Thu May 29 16:15:51 PDT 2014

The Buildbot has detected a new failure on builder phase2 - living while building lab.llvm.org.
Full details are available at:
 http://lab.llvm.org:8013/builders/phase2%20-%20living/builds/29

Buildbot URL: http://lab.llvm.org:8013/

Buildslave for this Build: macpro1

Build Reason: scheduler
Build Source Stamp: 209852
Blamelist: anemet,delesley,dnovillo,garious,gclayton,louis,tfiala

BUILD FAILED: failed

sincerely,
 -The Buildbot

================================================================================

CHANGES:
Files:
 docs/ReleaseNotes.rst
 docs/UsersManual.rst
On: smooshlab-project
At: Thu 29 May 2014 13:25:25
Changed By: dnovillo
Comments: Add documentation for -Rpass*

Summary:
This adds documentation for -Rpass, -Rpass-missed and -Rpass-analysis.
It also adds release notes for 3.5.

Reviewers: rsmith

Subscribers: cfe-commits

Differential Revision: http://reviews.llvm.org/D3730Properties: 
  phase_id: r209841-t20140529_133248-b214

Files:
 include/clang/Analysis/Analyses/ThreadSafetyTIL.h
 include/clang/Analysis/Analyses/ThreadSafetyTraverse.h
On: smooshlab-project
At: Thu 29 May 2014 13:41:25
Changed By: delesley
Comments: Thread Safety Analysis: minor changes to TIL pretty-printing.Properties: 
  phase_id: r209843-t20140529_134325-b215

Files:
 lib/Transforms/InstCombine/InstructionCombining.cpp
 test/Transforms/InstCombine/gepphigep.ll
On: smooshlab-project
At: Thu 29 May 2014 13:41:25
Changed By: louis
Comments: Add support for combining GEPs across PHI nodes

Currently LLVM will generally merge GEPs. This allows backends to use more
complex addressing modes. In some cases this is not happening because there
is PHI inbetween the two GEPs:

  GEP1--\
        |-->PHI1-->GEP3
  GEP2--/

This patch checks to see if GEP1 and GEP2 are similiar enough that they can be
cloned (GEP12) in GEP3's BB, allowing GEP->GEP merging (GEP123):

  GEP1--\                     --\                           --\
        |-->PHI1-->GEP3  ==>    |-->PHI2->GEP12->GEP3 == >    |-->PHI2->GEP123
  GEP2--/                     --/                           --/

This also breaks certain use chains that are preventing GEP->GEP merges that the
the existing instcombine would merge otherwise.

Tests included.Properties: 
  phase_id: r209843-t20140529_134325-b215

Files:
 test/tools/lldb-gdbserver/Makefile
 test/tools/lldb-gdbserver/TestLldbGdbServer.py
 test/tools/lldb-gdbserver/lldbgdbserverutils.py
 test/tools/lldb-gdbserver/main.cpp
 test/tools/lldb-gdbserver/socket_packet_pump.py
On: smooshlab-project
At: Thu 29 May 2014 13:55:25
Changed By: tfiala
Comments: gdb-remote testing: new test, cleaned up socket reading.

Added new SocketPacketPump class to decouple gdb remote packet
reading from packet expectations code.  This allowed for cleaner
implementation of the separate $O output streams (non-deterministic
packaging of inferior stdout/stderr) from all the rest of the packets.

Added a packet expectation matcher that can match expected accumulated
output with a timeout.  Use a dictionary with "type":"output_match".
See lldbgdbserverutils.MatchRemoteOutputEntry for details.

Added a gdb remote test to verify that $Hc (continue thread selection)
plus signal delivery ($C{signo}) works.  Having trouble getting this
to pass with debugserver on MacOSX 10.9.  Tried different variants,
including $vCont;C{signo}:{thread-id};c.  In some cases, I get the
test exe's signal handler to run ($vCont variant first time), in others I don't
($vCont second and further times).  $C{signo} doesn't hit the signal
handler code at all in the test exe but delivers a stop.  Further
$Hc and $C{signo} deliver the stop marking the wrong thread.  For now I'm
marking the test as XFAIL on dsym/debugserver.  Will revisit this on
lldb-dev.

Updated the text exe for these tests to support thread:print-ids (each
thread announces its thread id) and provide a SIGUSR1 thread handler
that prints out the thread id on which it was signaled.

Properties: 
  phase_id: r209845-t20140529_135726-b216

Files:
 include/clang/Basic/BuiltinsX86.def
 lib/Headers/avxintrin.h
 test/CodeGen/avx-shuffle-builtins.c
 test/CodeGen/builtins-x86.c
On: smooshlab-project
At: Thu 29 May 2014 14:01:25
Changed By: anemet
Comments: Implement AVX1 vbroadcast intrinsics with vector initializers

These intrinsics are special because they directly take a memory operand (AVX2
adds the register counterparts).  Typically, other non-memop intrinsics take
registers and then it's left to isel to fold memory operands.

In order to LICM intrinsics directly reading memory, we require that no stores
are in the loop (LICM) or that the folded load accesses constant memory
(MachineLICM).  When neither is the case we fail to hoist a loop-invariant
broadcast.

We can work around this limitation if we expose the load as a regular load and
then just implement the broadcast using the vector initializer syntax.  This
exposes the load to LICM and other optimizations.

At the IR level this is translated into a series of insertelements.  The
sequence is already recognized as a broadcast so there is no impact on the
quality of codegen.

_mm256_broadcast_pd and _mm256_broadcast_ps are not updated by this patch
because right now we lack the DAG-combiner smartness to recover the broadcast
instructions.  This will be tackled in a follow-on.

There will be completing changes on the LLVM side to remove the LLVM
intrinsics and to auto-upgrade bitcode files.

Fixes <rdar://problem/16494520>Properties: 
  phase_id: r209846-t20140529_140834-b217

Files:
 include/clang/Analysis/Analyses/ThreadSafetyTIL.h
 include/clang/Analysis/Analyses/ThreadSafetyTraverse.h
 include/clang/Analysis/Analyses/ThreadSafetyUtil.h
 lib/Analysis/ThreadSafetyCommon.cpp
On: smooshlab-project
At: Thu 29 May 2014 14:35:25
Changed By: delesley
Comments: Thread Safety Analysis: implement review suggestions from Aaron Ballman.Properties: 
  phase_id: r209847-t20140529_143725-b218

Files:
 CMakeLists.txt
 lib/lsan/CMakeLists.txt
 test/asan/CMakeLists.txt
 test/ubsan/CMakeLists.txt
On: smooshlab-project
At: Thu 29 May 2014 14:45:25
Changed By: garious
Comments: Revert "light up sanitizers for ARM"

This commit broke the Windows build, where CMAKE_C_COMPILER can
compile and link with -march=armv7-a but the just-built-clang
cannot.Properties: 
  phase_id: r209852-t20140529_144821-b219

Files:
 source/Core/ArchSpec.cpp
 source/Core/Module.cpp
 source/Host/macosx/Host.mm
 source/Plugins/ObjectFile/Mach-O/ObjectFileMachO.cpp
 source/Plugins/ObjectFile/Mach-O/ObjectFileMachO.h
 source/Plugins/Platform/MacOSX/PlatformiOSSimulator.cpp
 source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp
 tools/debugserver/source/RNBRemote.cpp
On: smooshlab-project
At: Thu 29 May 2014 14:45:25
Changed By: gclayton
Comments: iOS simulator cleanup to make sure we use "*-apple-ios" for iOS simulator apps and binaries.

Changes include:
- ObjectFileMachO can now determine if a binary is "*-apple-ios" or "*-apple-macosx" by checking the min OS and SDK load commands
- ArchSpec now says "<arch>-apple-macosx" is equivalent to "<arch>-apple-ios" since the simulator mixes and matches binaries (some from the system and most from the iOS SDK).
- Getting process inforamtion on MacOSX now correctly classifies iOS simulator processes so they have "*-apple-ios" architectures in the ProcessInstanceInfo
- PlatformiOSSimulator can now list iOS simulator processes correctly instead of showing nothing by using:
    (lldb) platform select ios-simulator
    (lldb) platform process list
- debugserver can now properly return "*-apple-ios" for the triple in the process info packets for iOS simulator executables
- GDBRemoteCommunicationClient now correctly passes along the triples it gets for process info by setting the OS in the llvm::Triple correctly

<rdar://problem/17060217>

Properties: 
  phase_id: r209852-t20140529_144821-b219

LOGS: