[llvm] [docs] Fix two stale file paths (PR #213994)

Hüseyin Kutsi Balcı via llvm-commits llvm-commits at lists.llvm.org
Wed Aug 26 01:15:35 PDT 2026


https://github.com/kutsibalci updated https://github.com/llvm/llvm-project/pull/213994

>From 5368a3ebc1a3dbcda54f41afe1a610037bfe0c7b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?H=C3=BCseyin=20Kutsi=20Balc=C4=B1?= <balcihkutsi at gmail.com>
Date: Wed, 26 Aug 2026 11:15:25 +0300
Subject: [PATCH] [docs] Fix two stale file paths

HowToSubmitABug.rst points at clang/utils/creduce-clang-crash.py. The
script was renamed to reduce-clang-crash.py in 59cee030f (#128592).

PdbStream.md points at llvm/DebugInfo/CodeView/CVDebugRecord.h. The
header moved to llvm/include/llvm/Object/CVDebugRecord.h in 211c67cdb.

Both replacement paths were checked to exist in the tree.
---
 llvm/docs/HowToSubmitABug.rst | 2 +-
 llvm/docs/PDB/PdbStream.md    | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/llvm/docs/HowToSubmitABug.rst b/llvm/docs/HowToSubmitABug.rst
index 10ded5c0bdd9f..e43bfa3e0341c 100644
--- a/llvm/docs/HowToSubmitABug.rst
+++ b/llvm/docs/HowToSubmitABug.rst
@@ -78,7 +78,7 @@ The `creduce <https://github.com/csmith-project/creduce>`_ tool helps to
 reduce the preprocessed file down to the smallest amount of code that still
 replicates the problem. You're encouraged to use creduce to reduce the code
 to make the developers' lives easier. The
-``clang/utils/creduce-clang-crash.py`` script can be used on the files
+``clang/utils/reduce-clang-crash.py`` script can be used on the files
 that clang dumps to help with automating creating a test to check for the
 compiler crash.
 
diff --git a/llvm/docs/PDB/PdbStream.md b/llvm/docs/PDB/PdbStream.md
index b3d93e1065695..7b9ace4a87e8b 100644
--- a/llvm/docs/PDB/PdbStream.md
+++ b/llvm/docs/PDB/PdbStream.md
@@ -139,7 +139,7 @@ directory". The exact format of a debug directory is described by the
 [IMAGE_DEBUG_DIRECTORY structure](<https://msdn.microsoft.com/en-us/library/windows/desktop/ms680307(v=vs.85).aspx>).
 For this particular case, the linker emits a debug directory of type
 `IMAGE_DEBUG_TYPE_CODEVIEW`. The format of this record is defined in
-`llvm/DebugInfo/CodeView/CVDebugRecord.h`, but it suffices to say here only
+`llvm/include/llvm/Object/CVDebugRecord.h`, but it suffices to say here only
 that it includes the same `Guid` and `Age` fields. At runtime, a
 debugger or tool can scan the COFF executable image for the presence of
 a debug directory of the correct type and verify that the Guid and Age match.



More information about the llvm-commits mailing list