After LLVM commit 434e4e15f6a3 ("[RISCV] Run MakeCompresible at Os as well (#207172)", 2026-07-06), I am seeing a boot hang with no output after OpenSBI when kCFI is enabled:
$ make -skj"$(nproc)" ARCH=riscv LLVM=1 mrproper defconfig
$ scripts/config -e CFI
$ make -skj"$(nproc)" ARCH=riscv LLVM=1 olddefconfig Image
$ boot-qemu.py -a riscv -k .
<hangs>
As this change should only impact files build with -Os, I built two sets of object files with compilers built from the problematic commit and its parent. I tried building with the -Os objects built using the parent commit compiler with the other objects built from the bad commit compiler to try and narrow things down but that did not fix the issue. CFI could be a red herring but it is the only configuration that appears to trigger this issue in my build tests.
After LLVM commit 434e4e15f6a3 ("[RISCV] Run MakeCompresible at Os as well (#207172)", 2026-07-06), I am seeing a boot hang with no output after OpenSBI when kCFI is enabled:
As this change should only impact files build with
-Os, I built two sets of object files with compilers built from the problematic commit and its parent. I tried building with the-Osobjects built using the parent commit compiler with the other objects built from the bad commit compiler to try and narrow things down but that did not fix the issue. CFI could be a red herring but it is the only configuration that appears to trigger this issue in my build tests.