[llvm-testresults] buildbot failure in smooshlab on clang-i386-darwin9

[daniel_dunbar at apple.com]

The Buildbot has detected a new failure of clang-i386-darwin9 on smooshlab.
Full details are available at:
 http://smooshlab.apple.com:8010/builders/clang-i386-darwin9/builds/8612

Buildbot URL: http://smooshlab.apple.com:8010/

Buildslave for this Build: smoosh-15.apple.com

Build Reason: 
Build Source Stamp: 103536
Blamelist: ddunbar,njeffords,rjmccall

BUILD FAILED: failed test-clang

sincerely,
 -The Buildbot


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

CHANGES:
File: include/llvm/MC/MCAssembler.h
At: Tue 11 May 2010 17:55:51
Changed By: njeffords
Comments: Added a trivial function to modify the flags field of MCSymbolData class. The function takes the value and a mask, and clears the mask bits before applying the value.Properties: 




Files:
 lib/Target/X86/AsmParser/X86AsmParser.cpp
 test/MC/AsmParser/X86/x86_64-suffix-matching.s
At: Tue 11 May 2010 17:55:51
Changed By: ddunbar
Comments: MC/X86: Extend suffix matching hack to match 'q' suffix.Properties: 




Files:
 include/clang/Basic/DiagnosticSemaKinds.td
 lib/Sema/JumpDiagnostics.cpp
 test/Sema/scope-check.c
 test/SemaCXX/scope-check.cpp
At: Tue 11 May 2010 18:01:43
Changed By: rjmccall
Comments: When checking scopes for indirect goto, be more permissive (but still safe)
about the permitted scopes.  Specifically:
  1) Permit labels and gotos to appear after a prologue of variable initializations.
  2) Permit indirect gotos to jump out of scopes that don't require cleanup.
  3) Diagnose possible attempts to indirect-jump out of scopes that do require
     cleanup.
This requires a substantial reinvention of the algorithm for checking indirect
goto.  The current algorithm is Omega(M*N), with M = the number of unique
scopes being jumped from and N = the number of unique scopes being jumped to,
with an additional factor that is probably (worst-case) linear in the depth
of scopes.  Thus the entire thing is likely cubic given some truly bizarre
ill-formed code;  on well-formed code the additional factor collapses to
an amortized constant (when amortized over the entire function) and so
the algorithm is quadratic.  Even this requires every label to appear in
its own scope, which would be very unusual for indirect-goto code (and
extremely unlikely for well-formed code);  it is far more likely that
all labels will be in the same scope and so the algorithm becomes linear.
For such a marginal feature, I am fairly happy with this result.

(this is using JumpDiagnostic's definition of scope, where successive
variables in a block appear in their own scope)

Properties: 




LOGS:
Last 10 lines of 'stdio':
	Testing Time: 82.31s
	********************
	Failing Tests (1):
	    Clang :: Sema/scope-check.c
	
	  Expected Passes    : 2227
	  Expected Failures  : 17
	  Unexpected Failures: 1
	make[1]: *** [all] Error 1
	make: *** [test] Error 2

Last 10 lines of 'warnings':
	1 warning and 18 errors generated.

Last 10 lines of 'fail':
	Clang :: Sema/scope-check.c

Last 10 lines of 'xfail':
	Clang :: CodeGenCXX/conversion-function.cpp
	Clang :: FixIt/fixit-errors.c
	Clang :: FixIt/fixit-pmem.cpp
	Clang :: FixIt/typo.m
	Clang :: PCH/changed-files.c
	Clang :: PCH/pr4489.c
	Clang :: PCH/source-manager-stack.c
	Clang :: SemaCXX/rval-references-xfail.cpp
	Clang :: SemaObjCXX/overload.mm
	Clang :: SemaTemplate/instantiate-function-1.mm

Last 10 lines of 'scope-check.c':
	--
	error: 'note' diagnostics expected but not seen: 
	  Line 22: jump bypasses initialization of declaration with __attribute__((cleanup))
	error: 'note' diagnostics seen but not expected: 
	  Line 22: jump bypasses initialization of variable with __attribute__((cleanup))
	1 warning and 18 errors generated.
	--
	
	********************