How does this interact with the CHECK-NOTs above it. Does it check that they don't appear before the __riscv_i but would be allowed after it?
~Craig On Tue, Feb 14, 2023 at 9:03 AM Alex Bradbury via cfe-commits < cfe-commits@lists.llvm.org> wrote: > > Author: Alex Bradbury > Date: 2023-02-14T17:02:32Z > New Revision: d05e1e99b1d62cf1f8ab37f83dd2f377328dd9c5 > > URL: > https://github.com/llvm/llvm-project/commit/d05e1e99b1d62cf1f8ab37f83dd2f377328dd9c5 > DIFF: > https://github.com/llvm/llvm-project/commit/d05e1e99b1d62cf1f8ab37f83dd2f377328dd9c5.diff > > LOG: [clang][test][RISCV] Check for __riscv_i in riscv-target-features.c > > This was overlooked, even though we have comprehensive tests for all the > other __riscv_fooext defines. > > Added: > > > Modified: > clang/test/Preprocessor/riscv-target-features.c > > Removed: > > > > > ################################################################################ > diff --git a/clang/test/Preprocessor/riscv-target-features.c > b/clang/test/Preprocessor/riscv-target-features.c > index 3f643a2fb587..139c84b08f16 100644 > --- a/clang/test/Preprocessor/riscv-target-features.c > +++ b/clang/test/Preprocessor/riscv-target-features.c > @@ -49,6 +49,7 @@ > // CHECK-NOT: __riscv_zcd {{.*$}} > // CHECK-NOT: __riscv_zcf {{.*$}} > // CHECK-NOT: __riscv_h {{.*$}} > +// CHECK: __riscv_i 2000000{{$}} > > // RUN: %clang -target riscv32-unknown-linux-gnu -march=rv32im -x c -E > -dM %s \ > // RUN: -o - | FileCheck --check-prefix=CHECK-M-EXT %s > > > > _______________________________________________ > cfe-commits mailing list > cfe-commits@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits >
_______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
