[llvm] [llvm-strings] Use small buffer instead of reading whole file (PR #163073)

Harald van Dijk via llvm-commits llvm-commits at lists.llvm.org
Thu Sep 24 07:24:26 PDT 2026


================
@@ -51,57 +43,28 @@
 ## before the chunk start and one after its end. The string is printed
 ## intact, once. The expected output is generated rather than written as a
 ## CHECK line because it is a chunk long.
-# RUN: %python %s 16383 S M at 16384 E 4 > %t.6
-# RUN: %python %s --line S M at 16384 E > %t.6.expected
+# RUN: printf "%16383sS%.16384dE%4s" | tr " " "\0" > %t.6
+# RUN: printf "S%.16384dE\n" > %t.6.expected
----------------
hvdijk wrote:

I can see that this issue, as well as the other one you mentioned, comes up with `printf.exe` supplied by GnuWin32. However, GnuWin32 has a big red warning on top of its webpage that "As of January 2024 this project is no longer functional. Please see the README for more information." Previously, up to LLVM 13, LLVM documented that GnuWin32 should be used (https://releases.llvm.org/13.0.0/docs/GettingStartedVS.html). This was changed in 2021, for LLVM 14, to say "You will need Git for Windows with bash tools, too." (https://releases.llvm.org/14.0.0/docs/GettingStartedVS.html) Can you please check that you're not still using the GnuWin32 tools?

https://github.com/llvm/llvm-project/pull/163073


More information about the llvm-commits mailing list