================
@@ -0,0 +1,16 @@
+/// Check "-fsycl-is-device" and the default triple "spirv64-unknown-unknown"
+// is passed when compiling for device.
+
+// RUN: %clang -### -fsycl -fsycl-device-only %s 2>&1 \
+// RUN: | FileCheck %s
+
+// CHECK: "-triple" "spirv64-unknown-unknown" {{.*}} "-fsycl-is-device"
+
+/// Check "-fsycl-is-device" and explicitly specified triple "nvptx" is
+// passed when compiling for device.
+
+// RUN: %clang -### -fsycl -fsycl-device-only --target=nvptx %s 2>&1 \
+// RUN: | FileCheck %s -check-prefix=TARGET
+//
+// TARGET: "-triple" "spirv32-unknown-unknown" "-aux-triple" "nvptx"
----------------
elizabethandrews wrote:
> For `nvptx64` the following is generated `"-triple" "spirv64-unknown-unknown"
> "-aux-triple" "nvptx64" `. I spoke to @mdtoguchi briefly and he had mentioned
> `--target=nvptx` is not really supported or tested yet. My understanding is
> that we do not support 3rd party targets at the moment and support for this
> will be added later down the line. So I do not know if it makes sense to test
> this now. I can modify this test use `spirv64`. This generates `"-triple"
> "spirv64-unknown-unknown" "-aux-triple" "spirv64"`. Would you prefer that?
https://github.com/llvm/llvm-project/pull/172366
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
