Update docs

Author: savannahostrowski

PCbuild/get_external.py

@@ -46,7 +46,9 @@ def fetch_zip(commit_hash, zip_dir, *, org='python', binary=False, verbose):
 
 def fetch_release(tag, tarball_dir, *, org='python', verbose=False):
     arch = platform.machine()
-    reporthook = print if verbose else None
+    reporthook = None
+    if verbose:
+        reporthook = print
     tarball_dir.mkdir(parents=True, exist_ok=True)
 
     arch_filename = f'{tag}-{arch}.tar.xz'

Tools/jit/jit_infra.md

@@ -8,21 +8,28 @@ When we update LLVM, we need to also update the LLVM release artifact for Window
 
 To update the LLVM release artifact for Windows builds, follow these steps:
 1. Go to the [LLVM releases page](https://github.com/llvm/llvm-project/releases).
-1. Download x86_64 Windows artifact for the desired LLVM version (e.g. `clang+llvm-21.1.4-x86_64-pc-windows-msvc.tar.xz`).
-1. Extract and repackage the tarball with the correct directory structure. For example:
+1. Download Windows artifacts for the desired LLVM version (e.g. `clang+llvm-21.1.4-x86_64-pc-windows-msvc.tar.xz` and `clang+llvm-21.1.4-aarch64-pc-windows-msvc.tar.xz`).
+1. Extract and repackage each tarball with the correct directory structure. For example:
    ```bash
+   # For x86_64 (AMD64)
    tar -xf clang+llvm-21.1.4-x86_64-pc-windows-msvc.tar.xz
    mv clang+llvm-21.1.4-x86_64-pc-windows-msvc llvm-21.1.4.0
-   tar -cf - llvm-21.1.4.0 | pv | xz > llvm-21.1.4.0.tar.xz  
+   tar -cf - llvm-21.1.4.0 | pv | xz > llvm-21.1.4.0-AMD64.tar.xz
+   rm -rf llvm-21.1.4.0
+
+   # For ARM64
+   tar -xf clang+llvm-21.1.4-aarch64-pc-windows-msvc.tar.xz
+   mv clang+llvm-21.1.4-aarch64-pc-windows-msvc llvm-21.1.4.0
+   tar -cf - llvm-21.1.4.0 | pv | xz > llvm-21.1.4.0-ARM64.tar.xz
    ```
-    The tarball must contain a top-level directory named `llvm-{version}.0/`.
+   Each tarball must contain a top-level directory named `llvm-{version}.0/`.
 1. Go to [cpython-bin-deps](https://github.com/python/cpython-bin-deps).
-1. Create a new release with the updated LLVM artifact.
+1. Create a new release with the LLVM artifacts.
     - Create a new tag to match the LLVM version (e.g. `llvm-21.1.4.0`).
-    - Specify the release title (e.g. `LLVM 21.1.4 for x86_64 Windows`).
-    - Upload the asset (you can leave all other fields the same).
+    - Specify the release title (e.g. `LLVM 21.1.4`).
+    - Upload both platform-specific assets to the same release.
 
 ### Other notes
 - You must make sure that the name of the artifact matches exactly what is expected in `Tools/jit/_llvm.py` and `PCbuild/get_externals.py`.
-- We don't need multiple release artifacts for each architecture because LLVM can cross-compile for different architectures on Windows; x86_64 is sufficient.
+- The artifact filename must include the architecture suffix (e.g. `llvm-21.1.4.0-AMD64.tar.xz`, `llvm-21.1.4.0-ARM64.tar.xz`). For backwards compatibility with older CPython branches, you can also upload a copy without the suffix (`llvm-21.1.4.0.tar.xz`).
 - You must have permissions to create releases in the `cpython-bin-deps` repository. If you don't have permissions, you should contact one of the organization admins.