vitalybuka wrote: > The above example doesn't reproduce the issue on clang as it reports errors via different pathways: You can probably trigger that path through ACCESS_MEMORY_RANGE and INTERCEPTORs? https://github.com/llvm/llvm-project/pull/144480