================ @@ -1,7 +1,10 @@ // REQUIRES: host-supports-jit // UNSUPPORTED: system-aix // RUN: cat %s | clang-repl | FileCheck %s -// RUN: cat %s | clang-repl -Xcc -O2 | FileCheck %s +// At -O2, somehow "x = 42" appears first when piped into FileCheck, +// see https://github.com/llvm/llvm-project/issues/143547. +// RUN: %if !system-windows %{ cat %s | clang-repl -Xcc -Xclang -Xcc -verify -Xcc -O2 | FileCheck %s %} ---------------- DavidSpickett wrote:
Good question: * It did not fail in pre-commit Windows CI. Which implies there are some Windows systems where it would not fail and would become a UPASS if we XFAIL'd it, but we could UNSUPPORTED instead. * The first RUN line does work consistently on all Windows machines we know of. XFAIL would disable the entire test. Which isn't a big loss given that we know the feature does work on Windows, but I tried to retain as much coverage as we could. https://github.com/llvm/llvm-project/pull/143851 _______________________________________________ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
