https://github.com/rnk created https://github.com/llvm/llvm-project/pull/228625
Replace same-project absolute URLs with relative source links or Sphinx cross-references in LLVM, Flang, libc, clang-tools-extra, and OpenMP. Use the explicit LangRef label for atomic.ignore.denormal.mode metadata. This lets Sphinx validate the targets and keeps local and archived documentation self-contained. Validation: docs-llvm-html, docs-llvm-man, docs-llvm-dwarfdump-man, docs-dsymutil-man, docs-flang-html, docs-flang-man, docs-clang-tools-html, docs-clang-tools-man, docs-libc-html, docs-openmp-html, and docs-openmp-man, followed by fresh Sphinx rebuilds (-E), on a merge of the three independent self-link fixes with the checker enabled and warnings-as-errors disabled. No self-link warnings or new warning messages compared with the audit baseline. Part of #214861 Assisted-by: Codex >From 98b222ea40948378a47585379546910ace6ffef2 Mon Sep 17 00:00:00 2001 From: Reid Kleckner <[email protected]> Date: Fri, 2 Oct 2026 23:37:21 +0000 Subject: [PATCH] [docs] Repair remaining absolute self-documentation links Replace same-project absolute URLs with relative source links or Sphinx cross-references in LLVM, Flang, libc, clang-tools-extra, and OpenMP. Use the explicit LangRef label for atomic.ignore.denormal.mode metadata. This lets Sphinx validate the targets and keeps local and archived documentation self-contained. Validation: docs-llvm-html, docs-llvm-man, docs-llvm-dwarfdump-man, docs-dsymutil-man, docs-flang-html, docs-flang-man, docs-clang-tools-html, docs-clang-tools-man, docs-libc-html, docs-openmp-html, and docs-openmp-man, followed by fresh Sphinx rebuilds (-E), on a merge of the three independent self-link fixes with the checker enabled and warnings-as-errors disabled. No self-link warnings or new warning messages compared with the audit baseline. Part of #214861 Assisted-by: Codex --- clang-tools-extra/Maintainers.md | 2 +- clang-tools-extra/docs/clang-tidy.md | 2 +- clang-tools-extra/docs/clang-tidy/Contributing.rst | 2 +- flang/docs/GettingInvolved.md | 2 +- flang/docs/GettingStarted.md | 2 +- libc/docs/dev/code_style.md | 8 ++++---- llvm/docs/AMDGPUUsage.rst | 4 ++-- openmp/docs/CommandLineArgumentReference.md | 4 ++-- 8 files changed, 13 insertions(+), 13 deletions(-) diff --git a/clang-tools-extra/Maintainers.md b/clang-tools-extra/Maintainers.md index 8830b86e09d7d17..5fb679f1e666d9d 100644 --- a/clang-tools-extra/Maintainers.md +++ b/clang-tools-extra/Maintainers.md @@ -2,7 +2,7 @@ This file is a list of the [maintainers](https://llvm.org/docs/DeveloperPolicy.html#maintainers) -for the [Extra Clang Tools](https://clang.llvm.org/extra/index.html) project. +for the {doc}`Extra Clang Tools </index>` project. # Active Maintainers diff --git a/clang-tools-extra/docs/clang-tidy.md b/clang-tools-extra/docs/clang-tidy.md index e1bab163a568541..6bc6e2d341ab234 100644 --- a/clang-tools-extra/docs/clang-tidy.md +++ b/clang-tools-extra/docs/clang-tidy.md @@ -7,4 +7,4 @@ orphan: true :http-equiv=refresh: 0;URL='clang-tidy/' ``` -clang-tidy documentation has moved here: <https://clang.llvm.org/extra/clang-tidy/> +clang-tidy documentation has moved here: [clang-tidy](clang-tidy/index.rst) diff --git a/clang-tools-extra/docs/clang-tidy/Contributing.rst b/clang-tools-extra/docs/clang-tidy/Contributing.rst index 1aafd7dc7faffc2..7534b69cec2f62b 100644 --- a/clang-tools-extra/docs/clang-tidy/Contributing.rst +++ b/clang-tools-extra/docs/clang-tidy/Contributing.rst @@ -442,7 +442,7 @@ Documenting your check ^^^^^^^^^^^^^^^^^^^^^^ The ``add_new_check.py`` script creates entries in the -`release notes <https://clang.llvm.org/extra/ReleaseNotes.html>`_, the list of +:doc:`release notes </ReleaseNotes>`, the list of checks and a new file for the check documentation itself. It is recommended that you have a concise summary of what your check does in a single sentence diff --git a/flang/docs/GettingInvolved.md b/flang/docs/GettingInvolved.md index 8126d2cad7faacf..fe346591d91d03e 100644 --- a/flang/docs/GettingInvolved.md +++ b/flang/docs/GettingInvolved.md @@ -73,7 +73,7 @@ Contributions to Flang are done using GitHub Pull Requests and follow the - Join [OpenMP in Flang Technical Call](https://bit.ly/39eQW3o) - Time: Biweekly call on Thursdays 7:30 AM Pacific time. Please check the [LLVM Community Calendar](https://calendar.google.com/calendar/u/0/[email protected]) for the next scheduled call. - Meeting minutes are [here](https://docs.google.com/document/d/1yA-MeJf6RYY-ZXpdol0t7YoDoqtwAyBhFLr5thu5pFI). -- Status tracking [page](https://flang.llvm.org/docs/OpenMPSupport.html). +- Status tracking [page](OpenMPSupport.md). ### OpenMP in LLVM Technical Call diff --git a/flang/docs/GettingStarted.md b/flang/docs/GettingStarted.md index cc3b6690d13a77a..9d621b2b7829f14 100644 --- a/flang/docs/GettingStarted.md +++ b/flang/docs/GettingStarted.md @@ -461,7 +461,7 @@ It will generate html in <build-dir>/tools/flang/docs/doxygen/html # for flang docs ``` ### Generate Sphinx-based Documentation -[Flang documentation](https://flang.llvm.org/docs/) should preferably be written in `markdown(.md)` syntax (they can be in `reStructuredText(.rst)` format as well but markdown is recommended in first place), it +[Flang documentation](index.md) should preferably be written in `markdown(.md)` syntax (they can be in `reStructuredText(.rst)` format as well but markdown is recommended in first place), it is mostly meant to be processed by the Sphinx documentation generation system to create HTML pages which would be hosted on the webpage of flang and updated periodically. diff --git a/libc/docs/dev/code_style.md b/libc/docs/dev/code_style.md index f403564fc5fd677..1eff90f0c408eff 100644 --- a/libc/docs/dev/code_style.md +++ b/libc/docs/dev/code_style.md @@ -178,14 +178,14 @@ not required. ## Warnings in sources We expect contributions to be free of warnings from the [minimum supported -compiler versions](https://libc.llvm.org/compiler_support.html#minimum-supported-versions) (and newer). +compiler versions](../compiler_support.md#minimum-supported-versions) (and newer). ## Header Inclusion Policy Because llvm-libc supports -[Overlay Mode](https://libc.llvm.org/overlay_mode.html), -[Full Host Build Mode](https://libc.llvm.org/full_host_build.html) and -[Full Cross Build Mode](https://libc.llvm.org/full_cross_build.html) care +[Overlay Mode](../overlay_mode.md), +[Full Host Build Mode](../full_host_build.md) and +[Full Cross Build Mode](../full_cross_build.md) care must be taken when `#include`'ing certain headers. The `include/` directory contains public facing headers that users must diff --git a/llvm/docs/AMDGPUUsage.rst b/llvm/docs/AMDGPUUsage.rst index b9c2e542fad4ba4..ec82f52027eddae 100644 --- a/llvm/docs/AMDGPUUsage.rst +++ b/llvm/docs/AMDGPUUsage.rst @@ -2553,8 +2553,8 @@ cases. This will typically be used in conjunction with ------------------------------------------ This is generic IR metadata for floating-point :ref:`atomicrmw -<i_atomicrmw>` operations; see `'atomic.ignore.denormal.mode' Metadata -<https://llvm.org/docs/LangRef.html#atomic-ignore-denormal-mode-metadata>`_ +<i_atomicrmw>` operations; see :ref:`'atomic.ignore.denormal.mode' Metadata +<md_atomic.ignore.denormal.mode>` in the language reference for its definition. It is required to emit a native atomic instruction for AMDGPU global memory, which unconditionally flushes float denormals. diff --git a/openmp/docs/CommandLineArgumentReference.md b/openmp/docs/CommandLineArgumentReference.md index 43e8ec514fa4ad8..e1edc3f2b887a08 100644 --- a/openmp/docs/CommandLineArgumentReference.md +++ b/openmp/docs/CommandLineArgumentReference.md @@ -182,7 +182,7 @@ environment variable `LIBOMPTARGET_DEVICE_RTL_DEBUG=<arg>`. Further, it is currently only supported for Nvidia targets as of July 2023. Alternatively, the environment variable `LIBOMPTARGET_DEBUG` can be set to debug both Nvidia and AMD GPU targets. For more information, see the -[debugging instructions](https://openmp.llvm.org/design/Runtimes.html#debugging). +[debugging instructions](design/Runtimes.md#debugging). The debugging instructions list the supported debugging arguments. ::: @@ -196,7 +196,7 @@ the target device. The optimization level can be set at runtime with `LIBOMPTARGET_JIT_OPT_LEVEL`, for instance, `LIBOMPTARGET_JIT_OPT_LEVEL=3` corresponding to optimizations level `-O3`. See the -[OpenMP JIT details](https://openmp.llvm.org/design/Runtimes.html#libomptarget-jit-pre-opt-ir-module) +[OpenMP JIT details](design/Runtimes.md#libomptarget-jit-pre-opt-ir-module) for instructions on extracting the embedded device code before or after the JIT and more. _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
