Build 9092 (which seems to have failed for other reasons) was at Clang r313352
Build 9093 used clang r313357


Nothing in that range looks suspicious:

------------------------------------------------------------------------
r313352 | ibiryukov | 2017-09-15 03:15:00 -0700 (Fri, 15 Sep 2017) | 5 lines

Revert "[SLPVectorizer] Failure to beneficially vectorize 'copyable' elements in integer binary ops."

This reverts commit r313348.

Reason: it caused buildbot failures.
------------------------------------------------------------------------
r313353 | rksimon | 2017-09-15 04:17:42 -0700 (Fri, 15 Sep 2017) | 3 lines

[X86][SSE] Add test cases vector for integer multiplies

Mainly inspired by PR34474 / D37896
------------------------------------------------------------------------
r313354 | krasimir | 2017-09-15 04:23:50 -0700 (Fri, 15 Sep 2017) | 22 lines

[clang-format] New flag - BraceWrapping.AfterExternBlock

Summary:
Bug: https://bugs.llvm.org/show_bug.cgi?id=34016 - **"extern C part"**

**Problem:**

Due to the lack of "brace wrapping extern" flag, clang format does parse the block after **extern** keyword moving the opening bracket to the header line always!

**Patch description:**

A new style added, new configuration flag - **BraceWrapping.AfterExternBlock** that allows us to decide whether we want a break before brace or not.

Reviewers: djasper, krasimir

Reviewed By: krasimir

Subscribers: klimek, cfe-commits

Differential Revision: https://reviews.llvm.org/D37845

Contributed by @PriMee!
------------------------------------------------------------------------
r313355 | alexfh | 2017-09-15 04:28:28 -0700 (Fri, 15 Sep 2017) | 24 lines

[clang-tidy] Fixed misc-unused-parameters omitting parameters square brackets

Summary:
Bug: https://bugs.llvm.org/show_bug.cgi?id=34449

**Problem:**

Clang-tidy check misc-unused-parameters comments out parameter name omitting following characters (e.g. square brackets) what results in its complete removal. Compilation errors might occur after clang-tidy fix as well.

**Patch description:**

Changed removal range. The range should end after parameter name, not after whole parameter declarator (which might be followed by e.g. square brackets).

Reviewers: alexfh

Reviewed By: alexfh

Subscribers: JDevlieghere, xazax.hun, cfe-commits

Tags: #clang-tools-extra

Patch by Pawel Maciocha!

Differential Revision: https://reviews.llvm.org/D37846
------------------------------------------------------------------------
r313356 | alexfh | 2017-09-15 04:45:30 -0700 (Fri, 15 Sep 2017) | 3 lines

Add a ReleaseNotes blurb for Execute.*Wait API change

... in r313155, r313156.
------------------------------------------------------------------------
r313357 | alexfh | 2017-09-15 04:45:57 -0700 (Fri, 15 Sep 2017) | 1 line

Remove unneeded forward declaration. NFC
------------------------------------------------------------------------

r313315 looks related, and the blame range is larger because 9092 failed for other reasons, right?

I think the nocompile expectations just need to be updated. The error is now:
fatal error: static_assert failed due to requirement 'param_is_forwardable' "..."

But the nocompile expectation is looking for:
fatal error: static_assert failed "..."

> r313315 looks related, and the blame range is larger because 9092 failed for other reasons, right?

Ah, yes.

For some reason, this doesn't repro locally for me. I must be holding it wrong somehow..

Aha, the nocompile tests don't respect clang_base_path:
https://cs.chromium.org/chromium/src/tools/nocompile_driver.py?rcl=07a8b4129c235bf171061472ca683a662fd9b316&l=214

  # TODO(ajwong): Get the compiler from gyp.
  cmdline = [os.path.join(os.path.dirname(os.path.realpath(__file__)),
                          '../third_party/llvm-build/Release+Asserts/bin',
                          'clang++')]

https://chromium-review.googlesource.com/c/chromium/src/+/668572

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/8023548f9723803b7b2dfdcb0cc2020011ea7867

commit 8023548f9723803b7b2dfdcb0cc2020011ea7867
Author: Hans Wennborg <hans@chromium.org>
Date: Fri Sep 15 18:34:51 2017

Fix base_nocompile_tests after Clang's static_assert wording changed

After Clang r313315, the static_assert errors look like:

  fatal error: static_assert failed due to requirement
  'param_is_forwardable' "Bound argument |i| of type |Arg| cannot be
  forwarded as [..]

instead of the previously expected:

  fatal error: static_assert failed "Bound argument |i| of type
  |Arg| cannot be forwarded as [..]

Since the test needs to work with both tip-of-tree and the currently
pinned version of Clang, add a regex to the expectations to make them
match both cases.

TBR=dcheng

Bug:  765692 
Change-Id: I6271fcdb8f346ffd359dd98f4bfcb32f5fdc9480
Reviewed-on: https://chromium-review.googlesource.com/668572
Reviewed-by: Hans Wennborg <hans@chromium.org>
Commit-Queue: Hans Wennborg <hans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#502315}
[modify] https://crrev.com/8023548f9723803b7b2dfdcb0cc2020011ea7867/base/bind_unittest.nc
[modify] https://crrev.com/8023548f9723803b7b2dfdcb0cc2020011ea7867/base/memory/ref_counted_unittest.nc
[modify] https://crrev.com/8023548f9723803b7b2dfdcb0cc2020011ea7867/base/memory/weak_ptr_unittest.nc