0

clang docs: link related documents from clang.md

I couldn't find the toolchain guarantees doc the other day, so as a first step
link to it here. We should probably reorganize the docs a bit -- the perf
regression bit in updating_clang.md looks like it belongs in the sheriffing
doc, and the "which files belong in the main package" should arguably move to
the toolchain guarantees doc.

Bug: none
Change-Id: I6b9018748c47f5942a970e8bcc76bcf1107784e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576583
Reviewed-by: Hans Wennborg <hans@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#834199}
This commit is contained in:
Nico Weber
2020-12-07 14:39:13 +00:00
committed by Chromium LUCI CQ
parent 40525f2d46
commit 46a1d77a23

@@ -88,3 +88,15 @@ Chromium tries to be buildable with its currently pinned clang, and with clang
trunk. Set `llvm_force_head_revision = true` in your args.gn if the clang you're trunk. Set `llvm_force_head_revision = true` in your args.gn if the clang you're
trying to build with is closer to clang trunk than to Chromium's pinned clang trying to build with is closer to clang trunk than to Chromium's pinned clang
(which `tools/clang/scripts/update.py --print-revision` prints). (which `tools/clang/scripts/update.py --print-revision` prints).
## Related documents
* [Toolchain support](toolchain_support.md) gives an overview of clang
rolls, and documents when to revert clang rolls and how to file good
toolchain bugs.
* [Updating clang](updating_clang.md) documents the mechanics of updating clang,
and which files are included in the default clang package.
* [Clang Sheriffing](clang_sheriffing.md) contains instructions for how to debug
compiler bugs, for clang sheriffs.