diff --git a/clang-tools-extra/clangd/Protocol.h b/clang-tools-extra/clangd/Protocol.h --- a/clang-tools-extra/clangd/Protocol.h +++ b/clang-tools-extra/clangd/Protocol.h @@ -7,7 +7,7 @@ //===----------------------------------------------------------------------===// // // This file contains structs based on the LSP specification at -// https://github.com/Microsoft/language-server-protocol/blob/master/protocol.md +// https://github.com/Microsoft/language-server-protocol/blob/main/protocol.md // // This is not meant to be a complete implementation, new interfaces are added // when they're needed. @@ -1172,7 +1172,7 @@ /// typing in one will update others too. /// /// See also: - /// https//github.com/Microsoft/vscode/blob/master/src/vs/editor/contrib/snippet/common/snippet.md + /// https://github.com/Microsoft/vscode/blob/main/src/vs/editor/contrib/snippet/snippet.md Snippet = 2, }; diff --git a/clang/docs/ClangFormatStyleOptions.rst b/clang/docs/ClangFormatStyleOptions.rst --- a/clang/docs/ClangFormatStyleOptions.rst +++ b/clang/docs/ClangFormatStyleOptions.rst @@ -149,7 +149,7 @@ `_ * ``Chromium`` A style complying with `Chromium's style guide - `_ + `_ * ``Mozilla`` A style complying with `Mozilla's style guide `_ diff --git a/clang/docs/LibFormat.rst b/clang/docs/LibFormat.rst --- a/clang/docs/LibFormat.rst +++ b/clang/docs/LibFormat.rst @@ -53,7 +53,7 @@ FormatStyle getGoogleStyle(); /// Returns a format style complying with Chromium's style guide: - /// https://chromium.googlesource.com/chromium/src/+/master/styleguide/styleguide.md + /// https://chromium.googlesource.com/chromium/src/+/refs/heads/main/styleguide/styleguide.md FormatStyle getChromiumStyle(); /// Returns a format style complying with the GNU coding standards: diff --git a/clang/docs/UsersManual.rst b/clang/docs/UsersManual.rst --- a/clang/docs/UsersManual.rst +++ b/clang/docs/UsersManual.rst @@ -3139,7 +3139,7 @@ Clang also supports language extensions documented in `The OpenCL C Language Extensions Documentation -`_. +`_. OpenCL-Specific Attributes -------------------------- diff --git a/clang/lib/AST/ItaniumMangle.cpp b/clang/lib/AST/ItaniumMangle.cpp --- a/clang/lib/AST/ItaniumMangle.cpp +++ b/clang/lib/AST/ItaniumMangle.cpp @@ -3572,7 +3572,7 @@ // mangling scheme, it will be specified in the next revision. The mangling // scheme is otherwise defined in the appendices to the Procedure Call Standard // for the Arm Architecture, see -// https://github.com/ARM-software/abi-aa/blob/master/aapcs64/aapcs64.rst#appendix-c-mangling +// https://github.com/ARM-software/abi-aa/blob/main/aapcs64/aapcs64.rst#appendix-c-mangling void CXXNameMangler::mangleAArch64FixedSveVectorType(const VectorType *T) { assert((T->getVectorKind() == VectorType::SveFixedLengthDataVector || T->getVectorKind() == VectorType::SveFixedLengthPredicateVector) && diff --git a/clang/lib/Format/Format.cpp b/clang/lib/Format/Format.cpp --- a/clang/lib/Format/Format.cpp +++ b/clang/lib/Format/Format.cpp @@ -1386,7 +1386,7 @@ ChromiumStyle.ContinuationIndentWidth = 8; ChromiumStyle.IndentWidth = 4; // See styleguide for import groups: - // https://chromium.googlesource.com/chromium/src/+/master/styleguide/java/java.md#Import-Order + // https://chromium.googlesource.com/chromium/src/+/refs/heads/main/styleguide/java/java.md#Import-Order ChromiumStyle.JavaImportGroups = { "android", "androidx", diff --git a/clang/lib/Format/FormatToken.h b/clang/lib/Format/FormatToken.h --- a/clang/lib/Format/FormatToken.h +++ b/clang/lib/Format/FormatToken.h @@ -1060,7 +1060,7 @@ bool IsJavaScriptIdentifier(const FormatToken &Tok, bool AcceptIdentifierName = true) const { // Based on the list of JavaScript & TypeScript keywords here: - // https://github.com/microsoft/TypeScript/blob/master/src/compiler/scanner.ts#L74 + // https://github.com/microsoft/TypeScript/blob/main/src/compiler/scanner.ts#L74 switch (Tok.Tok.getKind()) { case tok::kw_break: case tok::kw_case: diff --git a/clang/lib/Format/TokenAnnotator.cpp b/clang/lib/Format/TokenAnnotator.cpp --- a/clang/lib/Format/TokenAnnotator.cpp +++ b/clang/lib/Format/TokenAnnotator.cpp @@ -4061,7 +4061,7 @@ Keywords.kw_interface, Keywords.kw_type, Keywords.kw_var, Keywords.kw_let, tok::kw_const)) // See grammar for 'declare' statements at: - // https://github.com/Microsoft/TypeScript/blob/master/doc/spec.md#A.10 + // https://github.com/Microsoft/TypeScript/blob/main/doc/spec-ARCHIVED.md#A.10 return false; if (Left.isOneOf(Keywords.kw_module, tok::kw_namespace) && Right.isOneOf(tok::identifier, tok::string_literal)) diff --git a/clang/test/OpenMP/aarch64_vfabi_NarrowestDataSize.c b/clang/test/OpenMP/aarch64_vfabi_NarrowestDataSize.c --- a/clang/test/OpenMP/aarch64_vfabi_NarrowestDataSize.c +++ b/clang/test/OpenMP/aarch64_vfabi_NarrowestDataSize.c @@ -5,7 +5,7 @@ // Note: -fopemp and -fopenmp-simd behavior are expected to be the same. // This test checks the values of Narrowest Data Size (NDS), as defined in -// https://github.com/ARM-software/abi-aa/tree/master/vfabia64 +// https://github.com/ARM-software/abi-aa/tree/main/vfabia64 // // NDS is used to compute the token in the name of AdvSIMD // vector functions when no `simdlen` is specified, with the rule: diff --git a/clang/test/OpenMP/aarch64_vfabi_WidestDataSize.c b/clang/test/OpenMP/aarch64_vfabi_WidestDataSize.c --- a/clang/test/OpenMP/aarch64_vfabi_WidestDataSize.c +++ b/clang/test/OpenMP/aarch64_vfabi_WidestDataSize.c @@ -5,7 +5,7 @@ // Note: -fopemp and -fopenmp-simd behavior are expected to be the same. // This test checks the values of Widest Data Size (WDS), as defined -// in https://github.com/ARM-software/abi-aa/tree/master/vfabia64 +// in https://github.com/ARM-software/abi-aa/tree/main/vfabia64 // // WDS is used to check the accepted values of `simdlen()` when // targeting fixed-length SVE vector function names. The values of diff --git a/clang/www/related.html b/clang/www/related.html --- a/clang/www/related.html +++ b/clang/www/related.html @@ -39,8 +39,8 @@

Site: - - https://chromium.googlesource.com/chromium/src/+/master/docs/clang.md + + https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/clang.md

Notes on using Clang to build the Chromium web browser. diff --git a/libcxx/utils/ci/Dockerfile b/libcxx/utils/ci/Dockerfile --- a/libcxx/utils/ci/Dockerfile +++ b/libcxx/utils/ci/Dockerfile @@ -91,7 +91,7 @@ # Install the Buildkite agent and dependencies. This must be done as non-root # for the Buildkite agent to be installed in a path where we can find it. -RUN bash -c "$(curl -sL https://raw.githubusercontent.com/buildkite/agent/master/install.sh)" +RUN bash -c "$(curl -sL https://raw.githubusercontent.com/buildkite/agent/main/install.sh)" ENV PATH="${PATH}:/home/libcxx-builder/.buildkite-agent/bin" RUN echo "tags=\"queue=libcxx-builders,arch=$(uname -m),os=linux\"" >> "/home/libcxx-builder/.buildkite-agent/buildkite-agent.cfg" diff --git a/lld/docs/WebAssembly.rst b/lld/docs/WebAssembly.rst --- a/lld/docs/WebAssembly.rst +++ b/lld/docs/WebAssembly.rst @@ -205,6 +205,6 @@ supported. - No support for creating shared libraries. The spec for shared libraries in WebAssembly is still in flux: - https://github.com/WebAssembly/tool-conventions/blob/master/DynamicLinking.md + https://github.com/WebAssembly/tool-conventions/blob/main/DynamicLinking.md -.. _linking: https://github.com/WebAssembly/tool-conventions/blob/master/Linking.md +.. _linking: https://github.com/WebAssembly/tool-conventions/blob/main/Linking.md diff --git a/lld/wasm/Driver.cpp b/lld/wasm/Driver.cpp --- a/lld/wasm/Driver.cpp +++ b/lld/wasm/Driver.cpp @@ -632,7 +632,7 @@ // __table_base) from the environment and use these as the offset at // which to load our static data and function table. // See: - // https://github.com/WebAssembly/tool-conventions/blob/master/DynamicLinking.md + // https://github.com/WebAssembly/tool-conventions/blob/main/DynamicLinking.md auto *globalType = is64 ? &globalTypeI64 : &globalTypeI32; WasmSym::memoryBase = createUndefinedGlobal("__memory_base", globalType); WasmSym::tableBase = createUndefinedGlobal("__table_base", globalType); diff --git a/lld/wasm/SyntheticSections.h b/lld/wasm/SyntheticSections.h --- a/lld/wasm/SyntheticSections.h +++ b/lld/wasm/SyntheticSections.h @@ -71,7 +71,7 @@ // Create the custom "dylink" section containing information for the dynamic // linker. // See -// https://github.com/WebAssembly/tool-conventions/blob/master/DynamicLinking.md +// https://github.com/WebAssembly/tool-conventions/blob/main/DynamicLinking.md class DylinkSection : public SyntheticSection { public: DylinkSection() : SyntheticSection(llvm::wasm::WASM_SEC_CUSTOM, "dylink.0") {} diff --git a/lldb/unittests/Process/minidump/Inputs/linux-x86_64.cpp b/lldb/unittests/Process/minidump/Inputs/linux-x86_64.cpp --- a/lldb/unittests/Process/minidump/Inputs/linux-x86_64.cpp +++ b/lldb/unittests/Process/minidump/Inputs/linux-x86_64.cpp @@ -1,5 +1,5 @@ // Example source from breakpad's linux tutorial -// https://chromium.googlesource.com/breakpad/breakpad/+/master/docs/linux_starter_guide.md +// https://chromium.googlesource.com/breakpad/breakpad/+/main/docs/linux_starter_guide.md #include #include diff --git a/llvm/CMakeLists.txt b/llvm/CMakeLists.txt --- a/llvm/CMakeLists.txt +++ b/llvm/CMakeLists.txt @@ -804,7 +804,7 @@ endif() # For up-to-date instructions for installing the Tensorflow dependency, refer to -# the bot setup script: https://github.com/google/ml-compiler-opt/blob/master/buildbot/buildbot_init.sh +# the bot setup script: https://github.com/google/ml-compiler-opt/blob/main/buildbot/buildbot_init.sh # In this case, the latest C API library is available for download from # https://www.tensorflow.org/install/lang_c. # We will expose the conditional compilation variable, @@ -838,7 +838,7 @@ endif() # For up-to-date instructions for installing the Tensorflow dependency, refer to -# the bot setup script: https://github.com/google/ml-compiler-opt/blob/master/buildbot/buildbot_init.sh +# the bot setup script: https://github.com/google/ml-compiler-opt/blob/main/buildbot/buildbot_init.sh # Specifically, assuming python3 is installed: # python3 -m pip install --upgrade pip && python3 -m pip install --user tf_nightly==2.3.0.dev20200528 # Then set TENSORFLOW_AOT_PATH to the package install - usually it's ~/.local/lib/python3.7/site-packages/tensorflow diff --git a/llvm/docs/CompileCudaWithLLVM.rst b/llvm/docs/CompileCudaWithLLVM.rst --- a/llvm/docs/CompileCudaWithLLVM.rst +++ b/llvm/docs/CompileCudaWithLLVM.rst @@ -144,9 +144,9 @@ ---------------------------- In clang, ``math.h`` and ``cmath`` are available and `pass -`_ +`_ `tests -`_ +`_ adapted from libc++'s test suite. In nvcc ``math.h`` and ``cmath`` are mostly available. Versions of ``::foof`` diff --git a/llvm/docs/Proposals/TestSuite.rst b/llvm/docs/Proposals/TestSuite.rst --- a/llvm/docs/Proposals/TestSuite.rst +++ b/llvm/docs/Proposals/TestSuite.rst @@ -219,7 +219,7 @@ TVM ---- -https://github.com/dmlc/tvm/tree/master/apps/benchmark +https://github.com/dmlc/tvm/tree/main/apps/benchmark HydroBench ---------- @@ -227,7 +227,7 @@ ParRes ------ -https://github.com/ParRes/Kernels/tree/master/Cxx11 +https://github.com/ParRes/Kernels/tree/default/Cxx11 Applications/Libraries ====================== diff --git a/llvm/include/llvm/BinaryFormat/Wasm.h b/llvm/include/llvm/BinaryFormat/Wasm.h --- a/llvm/include/llvm/BinaryFormat/Wasm.h +++ b/llvm/include/llvm/BinaryFormat/Wasm.h @@ -7,7 +7,7 @@ //===----------------------------------------------------------------------===// // // This file defines manifest constants for the wasm object file format. -// See: https://github.com/WebAssembly/design/blob/master/BinaryEncoding.md +// See: https://github.com/WebAssembly/design/blob/main/BinaryEncoding.md // //===----------------------------------------------------------------------===// diff --git a/llvm/include/llvm/Object/Wasm.h b/llvm/include/llvm/Object/Wasm.h --- a/llvm/include/llvm/Object/Wasm.h +++ b/llvm/include/llvm/Object/Wasm.h @@ -9,7 +9,7 @@ // This file declares the WasmObjectFile class, which implements the ObjectFile // interface for Wasm files. // -// See: https://github.com/WebAssembly/design/blob/master/BinaryEncoding.md +// See: https://github.com/WebAssembly/design/blob/main/BinaryEncoding.md // //===----------------------------------------------------------------------===// diff --git a/llvm/lib/MC/WasmObjectWriter.cpp b/llvm/lib/MC/WasmObjectWriter.cpp --- a/llvm/lib/MC/WasmObjectWriter.cpp +++ b/llvm/lib/MC/WasmObjectWriter.cpp @@ -1087,7 +1087,7 @@ void WasmObjectWriter::writeRelocSection( uint32_t SectionIndex, StringRef Name, std::vector &Relocs) { - // See: https://github.com/WebAssembly/tool-conventions/blob/master/Linking.md + // See: https://github.com/WebAssembly/tool-conventions/blob/main/Linking.md // for descriptions of the reloc sections. if (Relocs.empty()) diff --git a/llvm/lib/Object/WasmObjectFile.cpp b/llvm/lib/Object/WasmObjectFile.cpp --- a/llvm/lib/Object/WasmObjectFile.cpp +++ b/llvm/lib/Object/WasmObjectFile.cpp @@ -359,7 +359,7 @@ Error WasmObjectFile::parseDylink0Section(ReadContext &Ctx) { // See - // https://github.com/WebAssembly/tool-conventions/blob/master/DynamicLinking.md + // https://github.com/WebAssembly/tool-conventions/blob/main/DynamicLinking.md HasDylinkSection = true; const uint8_t *OrigEnd = Ctx.End; diff --git a/llvm/lib/Target/WebAssembly/README.txt b/llvm/lib/Target/WebAssembly/README.txt --- a/llvm/lib/Target/WebAssembly/README.txt +++ b/llvm/lib/Target/WebAssembly/README.txt @@ -2,11 +2,11 @@ The object format emitted by the WebAssembly backed is documented in: - * https://github.com/WebAssembly/tool-conventions/blob/master/Linking.md + * https://github.com/WebAssembly/tool-conventions/blob/main/Linking.md The C ABI is described in: - * https://github.com/WebAssembly/tool-conventions/blob/master/BasicCABI.md + * https://github.com/WebAssembly/tool-conventions/blob/main/BasicCABI.md For more information on WebAssembly itself, see the home page: @@ -31,8 +31,8 @@ The following documents contain some information on the semantics and binary encoding of WebAssembly itself: - * https://github.com/WebAssembly/design/blob/master/Semantics.md - * https://github.com/WebAssembly/design/blob/master/BinaryEncoding.md + * https://github.com/WebAssembly/design/blob/main/Semantics.md + * https://github.com/WebAssembly/design/blob/main/BinaryEncoding.md Some notes on ways that the generated code could be improved follow: diff --git a/llvm/tools/vfabi-demangle-fuzzer/vfabi-demangler-fuzzer.cpp b/llvm/tools/vfabi-demangle-fuzzer/vfabi-demangler-fuzzer.cpp --- a/llvm/tools/vfabi-demangle-fuzzer/vfabi-demangler-fuzzer.cpp +++ b/llvm/tools/vfabi-demangle-fuzzer/vfabi-demangler-fuzzer.cpp @@ -34,7 +34,7 @@ const auto Info = VFABI::tryDemangleForVFABI(MangledName, *M); // Do not optimize away the return value. Inspired by - // https://github.com/google/benchmark/blob/master/include/benchmark/benchmark.h#L307-L345 + // https://github.com/google/benchmark/blob/main/include/benchmark/benchmark.h#L307-L345 asm volatile("" : : "r,m"(Info) : "memory"); return 0; diff --git a/llvm/utils/gn/README.rst b/llvm/utils/gn/README.rst --- a/llvm/utils/gn/README.rst +++ b/llvm/utils/gn/README.rst @@ -63,7 +63,7 @@ GN has extensive built-in help; try e.g. ``llvm/utils/gn/gn.py help gen`` to see the help for the ``gen`` command. The full GN reference is also `available -online `_. +online `_. GN has an autoformatter: ``git ls-files '*.gn' '*.gni' | xargs llvm/utils/gn/gn.py format`` diff --git a/mlir/docs/Dialects/SPIR-V.md b/mlir/docs/Dialects/SPIR-V.md --- a/mlir/docs/Dialects/SPIR-V.md +++ b/mlir/docs/Dialects/SPIR-V.md @@ -1422,8 +1422,8 @@ [GitHubLoweringTracking]: https://github.com/tensorflow/mlir/issues/303 [GenSpirvUtilsPy]: https://github.com/llvm/llvm-project/blob/main/mlir/utils/spirv/gen_spirv_dialect.py [CustomTypeAttrTutorial]: ../Tutorials/DefiningAttributesAndTypes.md -[VulkanExtensionPhysicalStorageBuffer]: https://github.com/KhronosGroup/SPIRV-Registry/blob/master/extensions/KHR/SPV_KHR_physical_storage_buffer.html -[VulkanExtensionVariablePointers]: https://github.com/KhronosGroup/SPIRV-Registry/blob/master/extensions/KHR/SPV_KHR_variable_pointers.html +[VulkanExtensionPhysicalStorageBuffer]: https://github.com/KhronosGroup/SPIRV-Registry/blob/main/extensions/KHR/SPV_KHR_physical_storage_buffer.html +[VulkanExtensionVariablePointers]: https://github.com/KhronosGroup/SPIRV-Registry/blob/main/extensions/KHR/SPV_KHR_variable_pointers.html [VulkanSpirv]: https://renderdoc.org/vkspec_chunked/chap40.html#spirvenv [VulkanShaderInterface]: https://renderdoc.org/vkspec_chunked/chap14.html#interfaces-resources [VulkanShaderInterfaceStorageClass]: https://renderdoc.org/vkspec_chunked/chap15.html#interfaces diff --git a/mlir/docs/LangRef.md b/mlir/docs/LangRef.md --- a/mlir/docs/LangRef.md +++ b/mlir/docs/LangRef.md @@ -3,7 +3,7 @@ MLIR (Multi-Level IR) is a compiler intermediate representation with similarities to traditional three-address SSA representations (like [LLVM IR](http://llvm.org/docs/LangRef.html) or -[SIL](https://github.com/apple/swift/blob/master/docs/SIL.rst)), but which +[SIL](https://github.com/apple/swift/blob/main/docs/SIL.rst)), but which introduces notions from polyhedral loop optimization as first-class concepts. This hybrid design is optimized to represent, analyze, and transform high level dataflow graphs as well as target-specific code generated for high performance diff --git a/mlir/docs/Rationale/Rationale.md b/mlir/docs/Rationale/Rationale.md --- a/mlir/docs/Rationale/Rationale.md +++ b/mlir/docs/Rationale/Rationale.md @@ -13,7 +13,7 @@ MLIR is a compiler intermediate representation with similarities to traditional three-address SSA representations (like [LLVM IR](http://llvm.org/docs/LangRef.html) or -[SIL](https://github.com/apple/swift/blob/master/docs/SIL.rst)), but which +[SIL](https://github.com/apple/swift/blob/main/docs/SIL.rst)), but which introduces notions from the polyhedral loop optimization works as first class concepts. This hybrid design is optimized to represent, analyze, and transform high level dataflow graphs as well as target-specific code generated for high @@ -195,10 +195,10 @@ [landingpad instruction](http://llvm.org/docs/LangRef.html#landingpad-instruction) is a hack used to represent this. MLIR doesn't make use of this capability, but SIL uses it extensively, e.g. in the - [switch_enum instruction](https://github.com/apple/swift/blob/master/docs/SIL.rst#switch-enum). + [switch_enum instruction](https://github.com/apple/swift/blob/main/docs/SIL.rst#switch-enum). For more context, block arguments were previously used in the Swift -[SIL Intermediate Representation](https://github.com/apple/swift/blob/master/docs/SIL.rst), +[SIL Intermediate Representation](https://github.com/apple/swift/blob/main/docs/SIL.rst), and described in [a talk on YouTube](https://www.youtube.com/watch?v=Ntj8ab-5cvE). The section of interest diff --git a/mlir/docs/Rationale/RationaleGenericDAGRewriter.md b/mlir/docs/Rationale/RationaleGenericDAGRewriter.md --- a/mlir/docs/Rationale/RationaleGenericDAGRewriter.md +++ b/mlir/docs/Rationale/RationaleGenericDAGRewriter.md @@ -102,7 +102,7 @@ LLVM's [DAG Combiner](https://github.com/llvm-mirror/llvm/blob/master/lib/CodeGen/SelectionDAG/DAGCombiner.cpp), the Swift compiler's -[SIL Combiner](https://github.com/apple/swift/tree/master/lib/SILOptimizer/SILCombiner), +[SIL Combiner](https://github.com/apple/swift/tree/main/lib/SILOptimizer/SILCombiner), etc. These generally match one or more operations and produce zero or more operations as a result. The LLVM [Legalization](https://github.com/llvm/llvm-project/tree/main/llvm/lib/CodeGen/SelectionDAG) diff --git a/mlir/include/mlir/Dialect/LLVMIR/ROCDLDialect.h b/mlir/include/mlir/Dialect/LLVMIR/ROCDLDialect.h --- a/mlir/include/mlir/Dialect/LLVMIR/ROCDLDialect.h +++ b/mlir/include/mlir/Dialect/LLVMIR/ROCDLDialect.h @@ -13,8 +13,8 @@ // pointed to here. However the following links contain more information about // ROCDL (ROCm-Device-Library) // -// https://github.com/RadeonOpenCompute/ROCm-Device-Libs/blob/master/doc/OCML.md -// https://github.com/RadeonOpenCompute/ROCm-Device-Libs/blob/master/doc/OCKL.md +// https://github.com/RadeonOpenCompute/ROCm-Device-Libs/blob/amd-stg-open/doc/OCML.md +// https://github.com/RadeonOpenCompute/ROCm-Device-Libs/blob/amd-stg-open/doc/OCKL.md // https://llvm.org/docs/AMDGPUUsage.html // //===----------------------------------------------------------------------===// diff --git a/mlir/lib/Tools/mlir-lsp-server/lsp/Protocol.h b/mlir/lib/Tools/mlir-lsp-server/lsp/Protocol.h --- a/mlir/lib/Tools/mlir-lsp-server/lsp/Protocol.h +++ b/mlir/lib/Tools/mlir-lsp-server/lsp/Protocol.h @@ -7,7 +7,7 @@ //===----------------------------------------------------------------------===// // // This file contains structs based on the LSP specification at -// https://github.com/Microsoft/language-server-protocol/blob/master/protocol.md +// https://github.com/Microsoft/language-server-protocol/blob/main/protocol.md // // This is not meant to be a complete implementation, new interfaces are added // when they're needed. diff --git a/utils/bazel/.bazelrc b/utils/bazel/.bazelrc --- a/utils/bazel/.bazelrc +++ b/utils/bazel/.bazelrc @@ -158,7 +158,7 @@ # Platform flags: # The toolchain container used for execution is defined in the target indicated # by "extra_execution_platforms", "host_platform" and "platforms". -# More about platforms: https://docs.bazel.build/versions/master/platforms.html +# More about platforms: https://docs.bazel.build/versions/main/platforms.html build:rbe --extra_toolchains=@rbe_default//config:cc-toolchain build:rbe --extra_execution_platforms=@rbe_default//config:platform build:rbe --host_platform=@rbe_default//config:platform diff --git a/utils/bazel/README.md b/utils/bazel/README.md --- a/utils/bazel/README.md +++ b/utils/bazel/README.md @@ -28,7 +28,7 @@ you don't have a checkout yet. 2. Install Bazel at the version indicated by [.bazelversion](./.bazelversion), following the official instructions, if you don't have it installed yet: - https://docs.bazel.build/versions/master/install.html. + https://docs.bazel.build/versions/main/install.html. 3. `cd utils/bazel` 4. `bazel build --config=generic_clang @llvm-project//...` (if building on Unix with Clang). `--config=generic_gcc` and `--config=msvc` are also available. @@ -45,7 +45,7 @@ ``` You can enable -[disk caching](https://docs.bazel.build/versions/master/remote-caching.html#disk-cache), +[disk caching](https://docs.bazel.build/versions/main/remote-caching.html#disk-cache), which will cache build results ```.bazelrc @@ -53,7 +53,7 @@ ``` You can instruct Bazel to use a ramdisk for its sandboxing operations via -[--sandbox_base](https://docs.bazel.build/versions/master/command-line-reference.html#flag--sandbox_base), +[--sandbox_base](https://docs.bazel.build/versions/main/command-line-reference.html#flag--sandbox_base), which can help avoid IO bottlenecks for the symlink stragegy used for sandboxing. This is especially important with many inputs and many cores (see https://github.com/bazelbuild/bazel/issues/11868):