================ @@ -64,6 +64,18 @@ // TARGETID-BOTH: "-target-feature" "+xnack" // TARGETID-BOTH-SAME: "-target-feature" "+sramecc" +// RUN: %clang -### --target=amdgcn-amd-amdhsa -mcpu=gfx1250:sramecc+ %s 2>&1 | \ +// RUN: FileCheck -check-prefix=SRAMECC-ON %s + +// RUN: %clang -### --target=amdgcn-amd-amdhsa -mcpu=gfx1250:sramecc- %s 2>&1 | \ +// RUN: FileCheck -check-prefix=SRAMECC-OFF %s + +// RUN: %clang -### --target=amdgcn-amd-amdhsa -mcpu=gfx1251:sramecc+ %s 2>&1 | \ +// RUN: FileCheck -check-prefix=SRAMECC-ON %s + +// RUN: %clang -### --target=amdgcn-amd-amdhsa -mcpu=gfx1251:sramecc- %s 2>&1 | \ +// RUN: FileCheck -check-prefix=SRAMECC-OFF %s ---------------- theSK2005 wrote:
Where in llvm would this test go? I don't fully understand why a clang test would go under the llvm either. https://github.com/llvm/llvm-project/pull/203313 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
