diff --git a/clang-tools-extra/clang-tidy/google/AvoidUnderscoreInGoogletestNameCheck.h b/clang-tools-extra/clang-tidy/google/AvoidUnderscoreInGoogletestNameCheck.h --- a/clang-tools-extra/clang-tidy/google/AvoidUnderscoreInGoogletestNameCheck.h +++ b/clang-tools-extra/clang-tidy/google/AvoidUnderscoreInGoogletestNameCheck.h @@ -17,7 +17,7 @@ namespace readability { // Check for underscores in the names of googletest tests, per -// https://github.com/google/googletest/blob/master/googletest/docs/faq.md#why-should-test-suite-names-and-test-names-not-contain-underscore +// https://github.com/google/googletest/blob/master/docs/faq.md#why-should-test-suite-names-and-test-names-not-contain-underscore /// /// For the user-facing documentation see: /// http://clang.llvm.org/extra/clang-tidy/checks/google-readability-avoid-underscore-in-googletest-name.html diff --git a/clang-tools-extra/clangd/README.md b/clang-tools-extra/clangd/README.md --- a/clang-tools-extra/clangd/README.md +++ b/clang-tools-extra/clangd/README.md @@ -5,7 +5,7 @@ - the **website** is https://clangd.llvm.org/. - the **bug tracker** is https://github.com/clangd/clangd/issues -- the **source code** is hosted at https://github.com/llvm/llvm-project/tree/master/clang-tools-extra/clangd. +- the **source code** is hosted at https://github.com/llvm/llvm-project/tree/main/clang-tools-extra/clangd. - the **website source code** is at https://github.com/llvm/clangd-www/ ### Communication channels diff --git a/clang-tools-extra/docs/clang-rename.rst b/clang-tools-extra/docs/clang-rename.rst --- a/clang-tools-extra/docs/clang-rename.rst +++ b/clang-tools-extra/docs/clang-rename.rst @@ -142,7 +142,7 @@ You can call :program:`clang-rename` directly from Vim! To set up :program:`clang-rename` integration for Vim see `clang/tools/clang-rename/clang-rename.py -`_. +`_. Please note that **you have to save all buffers, in which the replacement will happen before running the tool**. @@ -159,7 +159,7 @@ You can also use :program:`clang-rename` while using Emacs! To set up :program:`clang-rename` integration for Emacs see `clang-rename/tool/clang-rename.el -`_. +`_. Once installed, you can point your cursor to symbols you want to rename, press `M-X`, type `clang-rename` and new desired name. diff --git a/clang-tools-extra/docs/clang-tidy/Contributing.rst b/clang-tools-extra/docs/clang-tidy/Contributing.rst --- a/clang-tools-extra/docs/clang-tidy/Contributing.rst +++ b/clang-tools-extra/docs/clang-tidy/Contributing.rst @@ -128,7 +128,7 @@ Next, you need to decide which module the check belongs to. Modules are located in subdirectories of `clang-tidy/ -`_ +`_ and contain checks targeting a certain aspect of code quality (performance, readability, etc.), certain coding style or standard (Google, LLVM, CERT, etc.) or a widely used API (e.g. MPI). Their names are same as user-facing check @@ -211,7 +211,7 @@ (If you want to see an example of a useful check, look at `clang-tidy/google/ExplicitConstructorCheck.h -`_ +`_ and `clang-tidy/google/ExplicitConstructorCheck.cpp `_). diff --git a/clang-tools-extra/docs/clang-tidy/Integrations.rst b/clang-tools-extra/docs/clang-tidy/Integrations.rst --- a/clang-tools-extra/docs/clang-tidy/Integrations.rst +++ b/clang-tools-extra/docs/clang-tidy/Integrations.rst @@ -82,7 +82,7 @@ .. _ReSharper C++: https://www.jetbrains.com/help/resharper/Clang_Tidy_Integration.html .. _Visual Assist: https://docs.wholetomato.com/default.asp?W761 .. _Clang Power Tools: https://marketplace.visualstudio.com/items?itemName=caphyon.ClangPowerTools -.. _clang-tidy-vs: https://github.com/llvm/llvm-project/tree/master/clang-tools-extra/clang-tidy-vs +.. _clang-tidy-vs: https://github.com/llvm/llvm-project/tree/main/clang-tools-extra/clang-tidy-vs `MS Visual Studio`_ has a native clang-tidy-vs_ plugin and also can integrate :program:`clang-tidy` by means of three other tools. The `ReSharper C++`_ diff --git a/clang/docs/ClangPlugins.rst b/clang/docs/ClangPlugins.rst --- a/clang/docs/ClangPlugins.rst +++ b/clang/docs/ClangPlugins.rst @@ -111,7 +111,7 @@ target. To see a working example of an attribute plugin, see `the Attribute.cpp example -`_. +`_. Putting it all together ======================= @@ -119,7 +119,7 @@ Let's look at an example plugin that prints top-level function names. This example is checked into the clang repository; please take a look at the `latest version of PrintFunctionNames.cpp -`_. +`_. Running the plugin ================== @@ -160,7 +160,7 @@ -plugin -Xclang print-fns Also see the print-function-name plugin example's -`README `_ +`README `_ Using the clang command line diff --git a/clang/docs/ClangTools.rst b/clang/docs/ClangTools.rst --- a/clang/docs/ClangTools.rst +++ b/clang/docs/ClangTools.rst @@ -11,7 +11,7 @@ Only a couple of the most basic and fundamental tools are kept in the primary Clang tree. The rest of the tools are kept in a separate directory tree, `clang-tools-extra -`_. +`_. This document describes a high-level overview of the organization of Clang Tools within the project as well as giving an introduction to some diff --git a/clang/docs/ControlFlowIntegrityDesign.rst b/clang/docs/ControlFlowIntegrityDesign.rst --- a/clang/docs/ControlFlowIntegrityDesign.rst +++ b/clang/docs/ControlFlowIntegrityDesign.rst @@ -196,7 +196,7 @@ Vectors" above). The `GlobalLayoutBuilder`_ class is responsible for laying out the globals efficiently to minimize the sizes of the underlying bitsets. -.. _GlobalLayoutBuilder: https://github.com/llvm/llvm-project/blob/master/llvm/include/llvm/Transforms/IPO/LowerTypeTests.h +.. _GlobalLayoutBuilder: https://github.com/llvm/llvm-project/blob/main/llvm/include/llvm/Transforms/IPO/LowerTypeTests.h Alignment ~~~~~~~~~ @@ -300,7 +300,7 @@ In comparison, the old scheme does not require the splitting but it is more efficient when the combined virtual tables have been split. The `GlobalSplit`_ pass is responsible for splitting combined virtual tables into individual ones. -.. _GlobalSplit: https://github.com/llvm/llvm-project/blob/master/llvm/lib/Transforms/IPO/GlobalSplit.cpp +.. _GlobalSplit: https://github.com/llvm/llvm-project/blob/main/llvm/lib/Transforms/IPO/GlobalSplit.cpp Order virtual tables by a pre-order traversal of the class hierarchy ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/clang/docs/InternalsManual.rst b/clang/docs/InternalsManual.rst --- a/clang/docs/InternalsManual.rst +++ b/clang/docs/InternalsManual.rst @@ -2260,7 +2260,7 @@ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The first step to adding a new attribute to Clang is to add its definition to `include/clang/Basic/Attr.td -`_. +`_. This tablegen definition must derive from the ``Attr`` (tablegen, not semantic) type, or one of its derivatives. Most attributes will derive from the ``InheritableAttr`` type, which specifies that the attribute can be inherited by @@ -2328,10 +2328,10 @@ either ``diag::warn_attribute_wrong_decl_type`` or ``diag::err_attribute_wrong_decl_type``, and the parameter enumeration is found in `include/clang/Sema/ParsedAttr.h -`_ +`_ If a previously unused Decl node is added to the ``SubjectList``, the logic used to automatically determine the diagnostic parameter in `utils/TableGen/ClangAttrEmitter.cpp -`_ +`_ may need to be updated. By default, all subjects in the SubjectList must either be a Decl node defined @@ -2353,7 +2353,7 @@ Documentation is table generated on the public web server by a server-side process that runs daily. Generally, the documentation for an attribute is a stand-alone definition in `include/clang/Basic/AttrDocs.td -`_ +`_ that is named after the attribute being documented. If the attribute is not for public consumption, or is an implicitly-created @@ -2404,7 +2404,7 @@ optional. The associated C++ type of the argument is determined by the argument definition type. If the existing argument types are insufficient, new types can be created, but it requires modifying `utils/TableGen/ClangAttrEmitter.cpp -`_ +`_ to properly support the type. Other Properties @@ -2416,7 +2416,7 @@ If the parsed form of the attribute is more complex, or differs from the semantic form, the ``HasCustomParsing`` bit can be set to ``1`` for the class, and the parsing code in `Parser::ParseGNUAttributeArgs() -`_ +`_ can be updated for the special case. Note that this only applies to arguments with a GNU spelling -- attributes with a __declspec spelling currently ignore this flag and are handled by ``Parser::ParseMicrosoftDeclSpec``. @@ -2482,7 +2482,7 @@ Boilerplate ^^^^^^^^^^^ All semantic processing of declaration attributes happens in `lib/Sema/SemaDeclAttr.cpp -`_, +`_, and generally starts in the ``ProcessDeclAttribute()`` function. If the attribute has the ``SimpleHandler`` field set to ``1`` then the function to process the attribute will be automatically generated, and nothing needs to be @@ -2497,11 +2497,11 @@ If the attribute adds additional warnings, define a ``DiagGroup`` in `include/clang/Basic/DiagnosticGroups.td -`_ +`_ named after the attribute's ``Spelling`` with "_"s replaced by "-"s. If there is only a single diagnostic, it is permissible to use ``InGroup>`` directly in `DiagnosticSemaKinds.td -`_ +`_ All semantic diagnostics generated for your attribute, including automatically- generated ones (such as subjects and argument counts), should have a diff --git a/clang/docs/LibTooling.rst b/clang/docs/LibTooling.rst --- a/clang/docs/LibTooling.rst +++ b/clang/docs/LibTooling.rst @@ -198,4 +198,4 @@ For a list of libraries to link, look at one of the tools' CMake files (for example `clang-check/CMakeList.txt -`_). +`_). diff --git a/clang/lib/CodeGen/CGOpenMPRuntime.cpp b/clang/lib/CodeGen/CGOpenMPRuntime.cpp --- a/clang/lib/CodeGen/CGOpenMPRuntime.cpp +++ b/clang/lib/CodeGen/CGOpenMPRuntime.cpp @@ -442,7 +442,7 @@ /// Values for bit flags used in the ident_t to describe the fields. /// All enumeric elements are named and described in accordance with the code -/// from https://github.com/llvm/llvm-project/blob/master/openmp/runtime/src/kmp.h +/// from https://github.com/llvm/llvm-project/blob/main/openmp/runtime/src/kmp.h enum OpenMPLocationFlags : unsigned { /// Use trampoline for internal microtask. OMP_IDENT_IMD = 0x01, @@ -497,7 +497,7 @@ /// Describes ident structure that describes a source location. /// All descriptions are taken from -/// https://github.com/llvm/llvm-project/blob/master/openmp/runtime/src/kmp.h +/// https://github.com/llvm/llvm-project/blob/main/openmp/runtime/src/kmp.h /// Original structure: /// typedef struct ident { /// kmp_int32 reserved_1; /**< might be used in Fortran; @@ -4249,7 +4249,7 @@ // kmp_int32 flags, size_t sizeof_kmp_task_t, size_t sizeof_shareds, // kmp_routine_entry_t *task_entry); // Task flags. Format is taken from - // https://github.com/llvm/llvm-project/blob/master/openmp/runtime/src/kmp.h, + // https://github.com/llvm/llvm-project/blob/main/openmp/runtime/src/kmp.h, // description of kmp_tasking_flags struct. enum { TiedFlag = 0x1, diff --git a/clang/www/analyzer/checker_dev_manual.html b/clang/www/analyzer/checker_dev_manual.html --- a/clang/www/analyzer/checker_dev_manual.html +++ b/clang/www/analyzer/checker_dev_manual.html @@ -789,11 +789,11 @@
  • Xu, Zhongxing & Kremenek, Ted & Zhang, Jian. (2010). A Memory Model for Static Analysis of C Programs.
    • -
  • +
  • The Clang Static Analyzer README
    • -
  • +
  • Documentation for how the Store works
    • -
  • +
  • Documentation about inlining
  • The "Building a Checker in 24 hours" presentation given at the November 2012 LLVM Developer's diff --git a/clang/www/analyzer/open_projects.html b/clang/www/analyzer/open_projects.html --- a/clang/www/analyzer/open_projects.html +++ b/clang/www/analyzer/open_projects.html @@ -96,7 +96,7 @@ We should model (potentially some of) such evaluations, and the same applies for destructors called from operator delete[]. - See tests cases in handle_constructors_with_new_array.cpp. + See tests cases in handle_constructors_with_new_array.cpp.

    Constructing an array requires invoking multiple (potentially unknown) @@ -135,7 +135,7 @@

  • Handle constructors for default arguments

    Default arguments in C++ are recomputed at every call, and are therefore local, and not static, variables. - See tests cases in handle_constructors_for_default_arguments.cpp. + See tests cases in handle_constructors_for_default_arguments.cpp.

    Default arguments are annoying because the initializer expression is diff --git a/clang/www/hacking.html b/clang/www/hacking.html --- a/clang/www/hacking.html +++ b/clang/www/hacking.html @@ -89,7 +89,7 @@ wrapped Type* which you can then dump.

  • For LLDB users there are data formatters for clang data structures in - + clang/utils/ClangDataFormat.py.
    • @@ -98,9 +98,9 @@

    The files - + llvm/utils/LLVMVisualizers/llvm.natvis and - + clang/utils/ClangVisualizers/clang.natvis provide debugger visualizers that make debugging of more complex data types much easier.

    For Visual Studio 2013 only, put the files into diff --git a/clang/www/menu.html.incl b/clang/www/menu.html.incl --- a/clang/www/menu.html.incl +++ b/clang/www/menu.html.incl @@ -43,7 +43,7 @@

    Check Out Sources - Browse Sources + Browse Sources doxygen
    diff --git a/compiler-rt/include/sanitizer/tsan_interface_atomic.h b/compiler-rt/include/sanitizer/tsan_interface_atomic.h --- a/compiler-rt/include/sanitizer/tsan_interface_atomic.h +++ b/compiler-rt/include/sanitizer/tsan_interface_atomic.h @@ -30,7 +30,7 @@ #endif // Part of ABI, do not change. -// https://github.com/llvm/llvm-project/blob/master/libcxx/include/atomic +// https://github.com/llvm/llvm-project/blob/main/libcxx/include/atomic typedef enum { __tsan_memory_order_relaxed, __tsan_memory_order_consume, diff --git a/compiler-rt/lib/tsan/rtl/tsan_interface.h b/compiler-rt/lib/tsan/rtl/tsan_interface.h --- a/compiler-rt/lib/tsan/rtl/tsan_interface.h +++ b/compiler-rt/lib/tsan/rtl/tsan_interface.h @@ -204,7 +204,7 @@ #endif // Part of ABI, do not change. -// https://github.com/llvm/llvm-project/blob/master/libcxx/include/atomic +// https://github.com/llvm/llvm-project/blob/main/libcxx/include/atomic typedef enum { mo_relaxed, mo_consume, diff --git a/compiler-rt/www/menu.html.incl b/compiler-rt/www/menu.html.incl --- a/compiler-rt/www/menu.html.incl +++ b/compiler-rt/www/menu.html.incl @@ -13,6 +13,6 @@ llvm-dev llvm-commits Bug Reports - Browse Sources + Browse Sources diff --git a/flang/README.md b/flang/README.md --- a/flang/README.md +++ b/flang/README.md @@ -34,7 +34,7 @@ also review [how flang uses modern C++ features](docs/C++17.md). If you are interested in writing new documentation, follow -[markdown style guide from LLVM](https://github.com/llvm/llvm-project/blob/master/llvm/docs/MarkdownQuickstartTemplate.md). +[markdown style guide from LLVM](https://github.com/llvm/llvm-project/blob/main/llvm/docs/MarkdownQuickstartTemplate.md). ## Supported C++ compilers diff --git a/flang/docs/_templates/indexsidebar.html b/flang/docs/_templates/indexsidebar.html --- a/flang/docs/_templates/indexsidebar.html +++ b/flang/docs/_templates/indexsidebar.html @@ -4,21 +4,21 @@

    Documentation

    Getting Involved

    Additional Links

      -
    • Github Repository
      • +
    • Github Repository
    • Bug Reports
    • Code Review
      • diff --git a/flang/docs/flang-c-style.el b/flang/docs/flang-c-style.el --- a/flang/docs/flang-c-style.el +++ b/flang/docs/flang-c-style.el @@ -9,7 +9,7 @@ ;; Define a cc-mode style for editing C++ codes in Flang. ;; ;; Inspired from LLVM style in -;; https://github.com/llvm-mirror/llvm/blob/master/utils/emacs/emacs.el +;; https://github.com/llvm/llvm-project/blob/main/llvm/utils/emacs/emacs.el ;; (c-add-style "flang" diff --git a/libcxx/docs/index.rst b/libcxx/docs/index.rst --- a/libcxx/docs/index.rst +++ b/libcxx/docs/index.rst @@ -219,4 +219,4 @@ * `LLVM Bugzilla `_ * `libcxx-commits Mailing List`_ * `libcxx-dev Mailing List`_ -* `Browse libc++ Sources `_ +* `Browse libc++ Sources `_ diff --git a/libcxx/www/atomic_design.html b/libcxx/www/atomic_design.html --- a/libcxx/www/atomic_design.html +++ b/libcxx/www/atomic_design.html @@ -25,7 +25,7 @@ cfe-dev cfe-commits Bug Reports - Browse Sources + Browse Sources diff --git a/libcxx/www/atomic_design_a.html b/libcxx/www/atomic_design_a.html --- a/libcxx/www/atomic_design_a.html +++ b/libcxx/www/atomic_design_a.html @@ -25,7 +25,7 @@ cfe-dev cfe-commits Bug Reports - Browse Sources + Browse Sources diff --git a/libcxx/www/atomic_design_b.html b/libcxx/www/atomic_design_b.html --- a/libcxx/www/atomic_design_b.html +++ b/libcxx/www/atomic_design_b.html @@ -25,7 +25,7 @@ cfe-dev cfe-commits Bug Reports - Browse Sources + Browse Sources diff --git a/libcxx/www/atomic_design_c.html b/libcxx/www/atomic_design_c.html --- a/libcxx/www/atomic_design_c.html +++ b/libcxx/www/atomic_design_c.html @@ -25,7 +25,7 @@ cfe-dev cfe-commits Bug Reports - Browse Sources + Browse Sources diff --git a/libcxx/www/index.html b/libcxx/www/index.html --- a/libcxx/www/index.html +++ b/libcxx/www/index.html @@ -26,7 +26,7 @@ libcxx-dev libcxx-commits Bug Reports - Browse Sources + Browse Sources diff --git a/libcxx/www/ts1z_status.html b/libcxx/www/ts1z_status.html --- a/libcxx/www/ts1z_status.html +++ b/libcxx/www/ts1z_status.html @@ -25,7 +25,7 @@ cfe-dev cfe-commits Bug Reports - Browse Sources + Browse Sources diff --git a/libcxx/www/type_traits_design.html b/libcxx/www/type_traits_design.html --- a/libcxx/www/type_traits_design.html +++ b/libcxx/www/type_traits_design.html @@ -25,7 +25,7 @@ cfe-dev cfe-commits Bug Reports - Browse Sources + Browse Sources diff --git a/libcxx/www/upcoming_meeting.html b/libcxx/www/upcoming_meeting.html --- a/libcxx/www/upcoming_meeting.html +++ b/libcxx/www/upcoming_meeting.html @@ -25,7 +25,7 @@ cfe-dev cfe-commits Bug Reports - Browse Sources + Browse Sources diff --git a/libcxxabi/www/index.html b/libcxxabi/www/index.html --- a/libcxxabi/www/index.html +++ b/libcxxabi/www/index.html @@ -26,7 +26,7 @@ libcxx-dev libcxx-commits Bug Reports - Browse Sources + Browse Sources diff --git a/libunwind/docs/index.rst b/libunwind/docs/index.rst --- a/libunwind/docs/index.rst +++ b/libunwind/docs/index.rst @@ -101,4 +101,4 @@ * `LLVM Bugzilla `_ * `cfe-commits Mailing List`_ * `cfe-dev Mailing List`_ -* `Browse libunwind Sources `_ +* `Browse libunwind Sources `_ diff --git a/lldb/docs/resources/build.rst b/lldb/docs/resources/build.rst --- a/lldb/docs/resources/build.rst +++ b/lldb/docs/resources/build.rst @@ -12,7 +12,7 @@ general instructions on how to check out the LLVM monorepo, which contains the LLDB sources. -Git browser: https://github.com/llvm/llvm-project/tree/master/lldb +Git browser: https://github.com/llvm/llvm-project/tree/main/lldb Preliminaries ------------- @@ -326,7 +326,7 @@ A cache is passed to CMake with the ``-C`` flag, following the absolute path to the file on disk. Subsequent ``-D`` options are still allowed. Please find the currently available caches in the `lldb/cmake/caches/ -`_ +`_ directory. Common configurations on macOS diff --git a/lldb/docs/resources/test.rst b/lldb/docs/resources/test.rst --- a/lldb/docs/resources/test.rst +++ b/lldb/docs/resources/test.rst @@ -99,10 +99,10 @@ several extensions and custom test primitives on top of what's offered by `unittest2 `_. Those can be found in -`lldbtest.py `_. +`lldbtest.py `_. Below is the directory layout of the `example API test -`_. +`_. The test directory will always contain a python file, starting with ``Test``. Most of the tests are structured as a binary being debugged, so there will be one or more source files and a ``Makefile``. @@ -127,7 +127,7 @@ operations, such as creating targets, setting breakpoints etc. When code is shared across tests, we extract it into a utility in ``lldbutil``. It's always worth taking a look at `lldbutil -`_ +`_ to see if there's a utility to simplify some of the testing boiler plate. Because we can't always audit every existing test, this is doubly true when looking at an existing test for inspiration. @@ -168,7 +168,7 @@ include Makefile.rules Finding the right variables to set can be tricky. You can always take a look at -`Makefile.rules `_ +`Makefile.rules `_ but often it's easier to find an existing ``Makefile`` that does something similar to what you want to do. diff --git a/lldb/docs/use/python-reference.rst b/lldb/docs/use/python-reference.rst --- a/lldb/docs/use/python-reference.rst +++ b/lldb/docs/use/python-reference.rst @@ -420,11 +420,11 @@ There is a longer discussion of scripted thread plans and the state machine, and several interesting examples of their use in: -https://github.com/llvm/llvm-project/blob/master/lldb/examples/python/scripted_step.py +https://github.com/llvm/llvm-project/blob/main/lldb/examples/python/scripted_step.py And for a MUCH fuller discussion of the whole state machine, see: -https://github.com/llvm/llvm-project/blob/master/lldb/include/lldb/Target/ThreadPlan.h +https://github.com/llvm/llvm-project/blob/main/lldb/include/lldb/Target/ThreadPlan.h If you are reading those comments it is useful to know that scripted thread plans are set to be "MasterPlans", and not "OkayToDiscard". @@ -625,7 +625,7 @@ A more interesting template has been created in the source repository that can help you to create lldb command quickly: -https://github.com/llvm/llvm-project/blob/master/lldb/examples/python/cmdtemplate.py +https://github.com/llvm/llvm-project/blob/main/lldb/examples/python/cmdtemplate.py A commonly required facility is being able to create a command that does some token substitution, and then runs a different debugger command (usually, it diff --git a/llvm/docs/Vectorizers.rst b/llvm/docs/Vectorizers.rst --- a/llvm/docs/Vectorizers.rst +++ b/llvm/docs/Vectorizers.rst @@ -393,7 +393,7 @@ ----------- This section shows the execution time of Clang on a simple benchmark: -`gcc-loops `_. +`gcc-loops `_. This benchmarks is a collection of loops from the GCC autovectorization `page `_ by Dorit Nuzman. diff --git a/llvm/lib/CodeGen/GlobalISel/LegalizerHelper.cpp b/llvm/lib/CodeGen/GlobalISel/LegalizerHelper.cpp --- a/llvm/lib/CodeGen/GlobalISel/LegalizerHelper.cpp +++ b/llvm/lib/CodeGen/GlobalISel/LegalizerHelper.cpp @@ -5242,7 +5242,7 @@ // Expand f32 -> i64 conversion // This algorithm comes from compiler-rt's implementation of fixsfdi: - // https://github.com/llvm/llvm-project/blob/master/compiler-rt/lib/builtins/fixsfdi.c + // https://github.com/llvm/llvm-project/blob/main/compiler-rt/lib/builtins/fixsfdi.c unsigned SrcEltBits = SrcTy.getScalarSizeInBits(); diff --git a/llvm/lib/CodeGen/SelectionDAG/TargetLowering.cpp b/llvm/lib/CodeGen/SelectionDAG/TargetLowering.cpp --- a/llvm/lib/CodeGen/SelectionDAG/TargetLowering.cpp +++ b/llvm/lib/CodeGen/SelectionDAG/TargetLowering.cpp @@ -6514,7 +6514,7 @@ // Expand f32 -> i64 conversion // This algorithm comes from compiler-rt's implementation of fixsfdi: - // https://github.com/llvm/llvm-project/blob/master/compiler-rt/lib/builtins/fixsfdi.c + // https://github.com/llvm/llvm-project/blob/main/compiler-rt/lib/builtins/fixsfdi.c unsigned SrcEltBits = SrcVT.getScalarSizeInBits(); EVT IntVT = SrcVT.changeTypeToInteger(); EVT IntShVT = getShiftAmountTy(IntVT, DAG.getDataLayout()); diff --git a/llvm/test/Transforms/SLPVectorizer/AArch64/matmul.ll b/llvm/test/Transforms/SLPVectorizer/AArch64/matmul.ll --- a/llvm/test/Transforms/SLPVectorizer/AArch64/matmul.ll +++ b/llvm/test/Transforms/SLPVectorizer/AArch64/matmul.ll @@ -4,7 +4,7 @@ target datalayout = "e-m:e-i8:8:32-i16:16:32-i64:64-i128:128-n32:64-S128" ; This test is reduced from the matrix multiplication benchmark in the test-suite: -; https://github.com/llvm/llvm-test-suite/tree/master/SingleSource/Benchmarks/Misc/matmul_f64_4x4.c +; https://github.com/llvm/llvm-test-suite/tree/main/SingleSource/Benchmarks/Misc/matmul_f64_4x4.c ; The operations here are expected to be vectorized to <2 x double>. ; Otherwise, performance will suffer on Cortex-A53. diff --git a/llvm/utils/lit/setup.py b/llvm/utils/lit/setup.py --- a/llvm/utils/lit/setup.py +++ b/llvm/utils/lit/setup.py @@ -54,7 +54,7 @@ ====== The *lit* source is available as part of LLVM, in the LLVM source repository: -https://github.com/llvm/llvm-project/tree/master/llvm/utils/lit +https://github.com/llvm/llvm-project/tree/main/llvm/utils/lit """, classifiers=[ diff --git a/mlir/docs/DeclarativeRewrites.md b/mlir/docs/DeclarativeRewrites.md --- a/mlir/docs/DeclarativeRewrites.md +++ b/mlir/docs/DeclarativeRewrites.md @@ -740,4 +740,4 @@ details. [TableGen]: https://llvm.org/docs/TableGen/index.html -[OpBase]: https://github.com/llvm/llvm-project/blob/master/mlir/include/mlir/IR/OpBase.td +[OpBase]: https://github.com/llvm/llvm-project/blob/main/mlir/include/mlir/IR/OpBase.td 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 @@ -1387,7 +1387,7 @@ [SpirvTools]: https://github.com/KhronosGroup/SPIRV-Tools [Rationale]: ../Rationale/#block-arguments-vs-phi-nodes [ODS]: ../OpDefinitions.md -[GreedyPatternRewriter]: https://github.com/llvm/llvm-project/blob/master/mlir/lib/Transforms/Utils/GreedyPatternRewriteDriver.cpp +[GreedyPatternRewriter]: https://github.com/llvm/llvm-project/blob/main/mlir/lib/Transforms/Utils/GreedyPatternRewriteDriver.cpp [MlirDialectConversionTypeConversion]: ../DialectConversion.md#type-converter [MlirDialectConversionRewritePattern]: ../DialectConversion.md#conversion-patterns [MlirDialectConversionSignatureConversion]: ../DialectConversion.md#region-signature-conversion @@ -1399,26 +1399,26 @@ [MlirIndexType]: ../LangRef.md#index-type [MlirGpuDialect]: ../Dialects/GPU.md [MlirStandardDialect]: ../Dialects/Standard.md -[MlirSpirvHeaders]: https://github.com/llvm/llvm-project/tree/master/mlir/include/mlir/Dialect/SPIRV -[MlirSpirvLibs]: https://github.com/llvm/llvm-project/tree/master/mlir/lib/Dialect/SPIRV -[MlirSpirvTests]: https://github.com/llvm/llvm-project/tree/master/mlir/test/Dialect/SPIRV -[MlirSpirvUnittests]: https://github.com/llvm/llvm-project/tree/master/mlir/unittests/Dialect/SPIRV -[MlirGpuToSpirvHeaders]: https://github.com/llvm/llvm-project/tree/master/mlir/include/mlir/Conversion/GPUToSPIRV -[MlirGpuToSpirvLibs]: https://github.com/llvm/llvm-project/tree/master/mlir/lib/Conversion/GPUToSPIRV -[MlirStdToSpirvHeaders]: https://github.com/llvm/llvm-project/tree/master/mlir/include/mlir/Conversion/StandardToSPIRV -[MlirStdToSpirvLibs]: https://github.com/llvm/llvm-project/tree/master/mlir/lib/Conversion/StandardToSPIRV -[MlirSpirvDialect]: https://github.com/llvm/llvm-project/blob/master/mlir/include/mlir/Dialect/SPIRV/IR/SPIRVDialect.h -[MlirSpirvTypes]: https://github.com/llvm/llvm-project/blob/master/mlir/include/mlir/Dialect/SPIRV/IR/SPIRVTypes.h -[MlirSpirvOpsH]: https://github.com/llvm/llvm-project/blob/master/mlir/include/mlir/Dialect/SPIRV/IR/SPIRVOps.h -[MlirSpirvSerialization]: https://github.com/llvm/llvm-project/blob/master/mlir/include/mlir/Target/SPIRV/Serialization.h -[MlirSpirvBase]: https://github.com/llvm/llvm-project/blob/master/mlir/include/mlir/Dialect/SPIRV/IR/SPIRVBase.td -[MlirSpirvPasses]: https://github.com/llvm/llvm-project/blob/master/mlir/include/mlir/Dialect/SPIRV/Transforms/Passes.h -[MlirSpirvConversion]: https://github.com/llvm/llvm-project/blob/master/mlir/include/mlir/Dialect/SPIRV/Transforms/SPIRVConversion.h -[MlirSpirvAbi]: https://github.com/llvm/llvm-project/blob/master/mlir/include/mlir/Dialect/SPIRV/IR/TargetAndABI.h -[MlirSpirvOpsCpp]: https://github.com/llvm/llvm-project/blob/master/mlir/lib/Dialect/SPIRV/IR/SPIRVOps.cpp +[MlirSpirvHeaders]: https://github.com/llvm/llvm-project/tree/main/mlir/include/mlir/Dialect/SPIRV +[MlirSpirvLibs]: https://github.com/llvm/llvm-project/tree/main/mlir/lib/Dialect/SPIRV +[MlirSpirvTests]: https://github.com/llvm/llvm-project/tree/main/mlir/test/Dialect/SPIRV +[MlirSpirvUnittests]: https://github.com/llvm/llvm-project/tree/main/mlir/unittests/Dialect/SPIRV +[MlirGpuToSpirvHeaders]: https://github.com/llvm/llvm-project/tree/main/mlir/include/mlir/Conversion/GPUToSPIRV +[MlirGpuToSpirvLibs]: https://github.com/llvm/llvm-project/tree/main/mlir/lib/Conversion/GPUToSPIRV +[MlirStdToSpirvHeaders]: https://github.com/llvm/llvm-project/tree/main/mlir/include/mlir/Conversion/StandardToSPIRV +[MlirStdToSpirvLibs]: https://github.com/llvm/llvm-project/tree/main/mlir/lib/Conversion/StandardToSPIRV +[MlirSpirvDialect]: https://github.com/llvm/llvm-project/blob/main/mlir/include/mlir/Dialect/SPIRV/IR/SPIRVDialect.h +[MlirSpirvTypes]: https://github.com/llvm/llvm-project/blob/main/mlir/include/mlir/Dialect/SPIRV/IR/SPIRVTypes.h +[MlirSpirvOpsH]: https://github.com/llvm/llvm-project/blob/main/mlir/include/mlir/Dialect/SPIRV/IR/SPIRVOps.h +[MlirSpirvSerialization]: https://github.com/llvm/llvm-project/blob/main/mlir/include/mlir/Target/SPIRV/Serialization.h +[MlirSpirvBase]: https://github.com/llvm/llvm-project/blob/main/mlir/include/mlir/Dialect/SPIRV/IR/SPIRVBase.td +[MlirSpirvPasses]: https://github.com/llvm/llvm-project/blob/main/mlir/include/mlir/Dialect/SPIRV/Transforms/Passes.h +[MlirSpirvConversion]: https://github.com/llvm/llvm-project/blob/main/mlir/include/mlir/Dialect/SPIRV/Transforms/SPIRVConversion.h +[MlirSpirvAbi]: https://github.com/llvm/llvm-project/blob/main/mlir/include/mlir/Dialect/SPIRV/IR/TargetAndABI.h +[MlirSpirvOpsCpp]: https://github.com/llvm/llvm-project/blob/main/mlir/lib/Dialect/SPIRV/IR/SPIRVOps.cpp [GitHubDialectTracking]: https://github.com/tensorflow/mlir/issues/302 [GitHubLoweringTracking]: https://github.com/tensorflow/mlir/issues/303 -[GenSpirvUtilsPy]: https://github.com/llvm/llvm-project/blob/master/mlir/utils/spirv/gen_spirv_dialect.py +[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 diff --git a/mlir/docs/Dialects/Vector.md b/mlir/docs/Dialects/Vector.md --- a/mlir/docs/Dialects/Vector.md +++ b/mlir/docs/Dialects/Vector.md @@ -116,10 +116,10 @@ The list of Vector is currently undergoing evolutions and is best kept track of by following the evolution of the -[VectorOps.td](https://github.com/llvm/llvm-project/blob/master/mlir/include/mlir/Dialect/Vector/VectorOps.td) +[VectorOps.td](https://github.com/llvm/llvm-project/blob/main/mlir/include/mlir/Dialect/Vector/VectorOps.td) ODS file (markdown documentation is automatically generated locally when building and populates the [Vector -doc](https://github.com/llvm/llvm-project/blob/master/mlir/docs/Dialects/Vector.md)). Recent +doc](https://github.com/llvm/llvm-project/blob/main/mlir/docs/Dialects/Vector.md)). Recent extensions are driven by concrete use cases of interest. A notable such use case is the `vector.contract` op which applies principles of the StructuredOps abstraction to `vector` types. @@ -149,7 +149,7 @@ lowering](https://github.com/tensorflow/mlir/commit/957b1ca9680b4aacabb3a480fbc4ebd2506334b8)). Simple [conversion -tests](https://github.com/llvm/llvm-project/blob/master/mlir/test/Conversion/VectorToLLVM/vector-to-llvm.mlir) +tests](https://github.com/llvm/llvm-project/blob/main/mlir/test/Conversion/VectorToLLVM/vector-to-llvm.mlir) are available for the `LLVM` target starting from the Virtual Vector Level. ## Rationale @@ -225,7 +225,7 @@ Irrespective of the existence of an auto-vectorizer, one can build a notional vector language based on the VectorOps dialect and build end-to-end models with expressing `vector`s in the IR directly and simple -pattern-rewrites. [EDSC](https://github.com/llvm/llvm-project/blob/master/mlir/docs/EDSC.md)s +pattern-rewrites. [EDSC](https://github.com/llvm/llvm-project/blob/main/mlir/docs/EDSC.md)s provide a simple way of driving such a notional language directly in C++. ## Bikeshed Naming Discussion diff --git a/mlir/docs/OpDefinitions.md b/mlir/docs/OpDefinitions.md --- a/mlir/docs/OpDefinitions.md +++ b/mlir/docs/OpDefinitions.md @@ -1796,9 +1796,9 @@ [TableGen]: https://llvm.org/docs/TableGen/index.html [TableGenProgRef]: https://llvm.org/docs/TableGen/ProgRef.html [TableGenBackend]: https://llvm.org/docs/TableGen/BackEnds.html#introduction -[OpBase]: https://github.com/llvm/llvm-project/blob/master/mlir/include/mlir/IR/OpBase.td -[OpDefinitionsGen]: https://github.com/llvm/llvm-project/blob/master/mlir/tools/mlir-tblgen/OpDefinitionsGen.cpp -[EnumsGen]: https://github.com/llvm/llvm-project/blob/master/mlir/tools/mlir-tblgen/EnumsGen.cpp +[OpBase]: https://github.com/llvm/llvm-project/blob/main/mlir/include/mlir/IR/OpBase.td +[OpDefinitionsGen]: https://github.com/llvm/llvm-project/blob/main/mlir/tools/mlir-tblgen/OpDefinitionsGen.cpp +[EnumsGen]: https://github.com/llvm/llvm-project/blob/main/mlir/tools/mlir-tblgen/EnumsGen.cpp [StringAttr]: LangRef.md#string-attribute [IntegerAttr]: LangRef.md#integer-attribute -[AttrClasses]: https://github.com/llvm/llvm-project/blob/master/mlir/include/mlir/IR/Attributes.h +[AttrClasses]: https://github.com/llvm/llvm-project/blob/main/mlir/include/mlir/IR/Attributes.h diff --git a/mlir/docs/PatternRewriter.md b/mlir/docs/PatternRewriter.md --- a/mlir/docs/PatternRewriter.md +++ b/mlir/docs/PatternRewriter.md @@ -114,7 +114,7 @@ class. This is required because the underlying pattern driver may have state that would be invalidated when a mutation takes place. Examples of some of the more prevalent `PatternRewriter` API is shown below, please refer to the -[class documentation](https://github.com/llvm/llvm-project/blob/master/mlir/include/mlir/IR/PatternMatch.h#L235) +[class documentation](https://github.com/llvm/llvm-project/blob/main/mlir/include/mlir/IR/PatternMatch.h#L235) for a more up-to-date listing of the available API: * Erase an Operation : `eraseOp` 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 @@ -97,7 +97,7 @@ GCC ["combine" routines](https://github.com/gcc-mirror/gcc/blob/master/gcc/combine.c) (which try to merge two machine instructions into a single one), the LLVM -[Inst Combine](https://github.com/llvm/llvm-project/tree/master/llvm/lib/Transforms/InstCombine) +[Inst Combine](https://github.com/llvm/llvm-project/tree/main/llvm/lib/Transforms/InstCombine) [pass](https://llvm.org/docs/Passes.html#instcombine-combine-redundant-instructions), LLVM's [DAG Combiner](https://github.com/llvm-mirror/llvm/blob/master/lib/CodeGen/SelectionDAG/DAGCombiner.cpp), @@ -105,7 +105,7 @@ [SIL Combiner](https://github.com/apple/swift/tree/master/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/master/llvm/lib/CodeGen/SelectionDAG) +[Legalization](https://github.com/llvm/llvm-project/tree/main/llvm/lib/CodeGen/SelectionDAG) infrastructure has a different outer loop but otherwise works the same way. These passes have a lot of diversity, but also have a unifying structure: they @@ -184,7 +184,7 @@ This example defines a matcher for the ["blci" instruction](https://en.wikipedia.org/wiki/Bit_Manipulation_Instruction_Sets#TBM_\(Trailing_Bit_Manipulation\)) in the -[X86 target description](https://github.com/llvm/llvm-project/blob/master/llvm/lib/Target/X86/X86InstrInfo.td), +[X86 target description](https://github.com/llvm/llvm-project/blob/main/llvm/lib/Target/X86/X86InstrInfo.td), there are many others in that file (look for `Pat<>` patterns, since they aren't entangled in details of the compiler like assembler/disassembler generation logic). diff --git a/mlir/docs/SPIRVToLLVMDialectConversion.md b/mlir/docs/SPIRVToLLVMDialectConversion.md --- a/mlir/docs/SPIRVToLLVMDialectConversion.md +++ b/mlir/docs/SPIRVToLLVMDialectConversion.md @@ -951,4 +951,4 @@ [LLVMFunctionAttributes]: https://llvm.org/docs/LangRef.html#function-attributes [SPIRVFunctionAttributes]: https://www.khronos.org/registry/spir-v/specs/unified1/SPIRV.html#_a_id_function_control_a_function_control -[VulkanLayoutUtils]: https://github.com/llvm/llvm-project/blob/master/mlir/include/mlir/Dialect/SPIRV/LayoutUtils.h +[VulkanLayoutUtils]: https://github.com/llvm/llvm-project/blob/main/mlir/include/mlir/Dialect/SPIRV/LayoutUtils.h diff --git a/mlir/docs/ShapeInference.md b/mlir/docs/ShapeInference.md --- a/mlir/docs/ShapeInference.md +++ b/mlir/docs/ShapeInference.md @@ -291,5 +291,5 @@ the shape function. The reference implementation is general and can support the arbitrary computations needed to specify output shapes. -[InferTypeOpInterface]: https://github.com/llvm/llvm-project/tree/master/mlir/include/mlir/Interfaces/InferTypeOpInterface.td -[ShapedType]: https://github.com/llvm/llvm-project/tree/master/mlir/include/mlir/IR/BuiltinTypes.h +[InferTypeOpInterface]: https://github.com/llvm/llvm-project/tree/main/mlir/include/mlir/Interfaces/InferTypeOpInterface.td +[ShapedType]: https://github.com/llvm/llvm-project/tree/main/mlir/include/mlir/IR/BuiltinTypes.h diff --git a/mlir/docs/Tutorials/UnderstandingTheIRStructure.md b/mlir/docs/Tutorials/UnderstandingTheIRStructure.md --- a/mlir/docs/Tutorials/UnderstandingTheIRStructure.md +++ b/mlir/docs/Tutorials/UnderstandingTheIRStructure.md @@ -86,7 +86,7 @@ ``` The code for the pass is available -[here in the repo](https://github.com/llvm/llvm-project/blob/master/mlir/test/lib/IR/TestPrintNesting.cpp) +[here in the repo](https://github.com/llvm/llvm-project/blob/main/mlir/test/lib/IR/TestPrintNesting.cpp) and can be exercised with `mlir-opt -test-print-nesting`. ### Example @@ -273,7 +273,7 @@ ``` The illustrating code for this pass is available -[here in the repo](https://github.com/llvm/llvm-project/blob/master/mlir/test/lib/IR/TestPrintDefUse.cpp) +[here in the repo](https://github.com/llvm/llvm-project/blob/main/mlir/test/lib/IR/TestPrintDefUse.cpp) and can be exercised with `mlir-opt -test-print-defuse`. The chaining of `Value`s and their uses can be viewed as following: diff --git a/openmp/www/index.html b/openmp/www/index.html --- a/openmp/www/index.html +++ b/openmp/www/index.html @@ -25,7 +25,7 @@ openmp-dev openmp-commits Bug Reports - Browse Sources + Browse Sources diff --git a/polly/www/menu.html.incl b/polly/www/menu.html.incl --- a/polly/www/menu.html.incl +++ b/polly/www/menu.html.incl @@ -34,7 +34,7 @@ Code Coverage Static analysis Doxygen - Source @ GitHub + Source @ GitHub