Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Driver][SYCL] Support 64bit long double for SYCL GPU compilation #16441

Open
wants to merge 2 commits into
base: sycl
Choose a base branch
from

Conversation

jchlanda
Copy link
Contributor

Make sure that -mlong-double-64 option is supported on HIP/Cuda.

@jchlanda jchlanda requested a review from a team as a code owner December 20, 2024 14:20
@jchlanda
Copy link
Contributor Author

Fixes: #15852

@jchlanda
Copy link
Contributor Author

Looks like linux gen12 is experiencing some problems.


// RUN: not %clangxx -c -fsycl -mlong-double-80 -target nvptx64-nvidia-cuda %s -### 2>&1 | FileCheck --check-prefix=CHECK-80-NVPTX %s
// CHECK-80-NVPTX: error: unsupported option '-mlong-double-80' for target 'nvptx64-nvidia-cuda'
// CHECK-80-NVPTX-NOT: clang{{.*}} "-triple" "-nvptx64-nvidia-cuda" {{.*}} "-mlong-double-80"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For all of these, I believe the expected option syntax is to use --target=x86_64-unknown-linux-gnu -fsycl-targets=nvptx64-nvidia-cuda. Use of --target=<triple> is preferred over -target <triple> moving forward.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. I've only updated tests that I've added in this patch.

As a side note, it seems strange that sycl target triple option gets only one hyphen, both seem to be following the same pattern of:

hyphen[hyphen]target_name=triple

but end up spelled out differently:

--target=<triple>

vs:

-fsycl-targets=<triple>

clang/test/Driver/sycl-mlong-double.cpp Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants