[Docs] Fix broken LLVM doc pages (#68631)
This commit is contained in:
@@ -20,7 +20,7 @@ Requirements for *new* repositories as part of the
|
||||
|
||||
If you want to integrate your project as part of the Monorepo, please take a
|
||||
look at the
|
||||
[Developer Policy](DeveloperPolicy.html#adding-an-established-project-to-the-llvm-monorepo>).
|
||||
[Developer Policy](project:DeveloperPolicy.rst#Adding an Established Project To the LLVM Monorepo).
|
||||
|
||||
To request a new repository, please create an issue with the
|
||||
[Infrastructure Working Group](https://github.com/llvm/llvm-iwg/issues).
|
||||
|
||||
@@ -191,4 +191,4 @@ instruction number of any cloned instruction, to avoid duplicate numbers
|
||||
appearing to `LiveDebugValues`. Dealing with duplicated instructions is a
|
||||
natural extension to instruction referencing that's currently unimplemented.
|
||||
|
||||
[LiveDebugValues]: SourceLevelDebugging.html#livedebugvalues-expansion-of-variable-locations
|
||||
[LiveDebugValues]: project:SourceLevelDebugging.rst#LiveDebugValues expansion of variable locations
|
||||
|
||||
@@ -158,4 +158,4 @@ integration documentation can be found in the [myst-parser docs].
|
||||
|
||||
## Generating the documentation
|
||||
|
||||
see [Sphinx Quickstart Template](SphinxQuickstartTemplate.html#generating-the-documentation)
|
||||
see [Sphinx Quickstart Template](project:SphinxQuickstartTemplate.rst#Generating the documentation)
|
||||
|
||||
@@ -303,8 +303,7 @@ instructions as such:
|
||||
|
||||
#### Assembly Representation
|
||||
|
||||
At the assembly level,
|
||||
[Authenticated Relocations](#authenticated-global-relocation) are represented
|
||||
At the assembly level, authenticated relocations are represented
|
||||
using the `@AUTH` modifier:
|
||||
|
||||
```asm
|
||||
@@ -328,8 +327,7 @@ For example:
|
||||
|
||||
#### ELF Object File Representation
|
||||
|
||||
At the object file level,
|
||||
[Authenticated Relocations](#authenticated-global-relocation) are represented
|
||||
At the object file level, authenticated relocations are represented
|
||||
using the `R_AARCH64_AUTH_ABS64` relocation kind (with value `0xE100`).
|
||||
|
||||
The signing schema is encoded in the place of relocation to be applied
|
||||
|
||||
Reference in New Issue
Block a user