melver added a comment. In D79628#2058404 <https://reviews.llvm.org/D79628#2058404>, @vvereschaka wrote:
> the Clang sanitize-coverage.c test gets crashed on Windows platform for armv7 > target: > > - FAIL: Clang::sanitize-coverage.c > > ``` > - command stderr: Pass 'Run-time bounds checking' is not initialized. > > Verify if there is a pass dependency cycle. > > Required Passes: > > Target Library Information ... ``` see more details here: > http://lab.llvm.org:8011/builders/llvm-clang-win-x-armv7l/builds/7561/steps/test-check-clang/logs/FAIL%3A%20Clang%3A%3Asanitize-coverage.c > > The first failed build: > http://lab.llvm.org:8011/builders/llvm-clang-win-x-armv7l/builds/7561 > > Would you take care of it? Thanks, I've been trying to understand this (similar failures on other armv7 instances). What's different with LLVM on armv7? Does it use a differently configured pass manager? Given this only fails on armv7, to me this highlights an issue with the architecture. What I can do is blacklist the test for armv7 and thumbv7 until those architectures get fixed. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D79628/new/ https://reviews.llvm.org/D79628 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
