Skip to content

[SYCL] Remove HIP Nvidia tests/CI support #16611

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

Merged
merged 5 commits into from
Jan 14, 2025

Conversation

aelovikov-intel
Copy link
Contributor

@aelovikov-intel aelovikov-intel commented Jan 13, 2025

As noted in #14432 the configuration isn't supported/tested anymore and there were some PRs removing related XFAILs (#16287, #16307, and possibly others).

This PR goes a step further and removes all the support for that configuration in our LIT tests.

As noted in intel#14432 the configuration
isn't supported/tested anymore and there were some PRs removing related
`XFAIL`s (intel#16287,
intel#16307, and possibly others).

This PR goes a step further removes all the support for that
configuration.
@@ -168,7 +168,7 @@

if "amdgcn-amd-amdhsa" in triple:
llvm_config.with_system_environment("ROCM_PATH")
config.available_features.add("hip_amd")
config.available_features.add("hip")
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we move this change to a separate commit or even PR?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't see how, but maybe I don't fully understand the question.

Copy link
Contributor

Choose a reason for hiding this comment

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

If I get it right, this change renames hip_amd lit feature into hip. The renaming makes sense to me, but it's not necessary for removing "HIP NVIDIA infrastructure support". The change contributes a significant part of changes to the diff, which will be easier to review separately.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

In practice that might be true, but in theory/semantically it's only possible after hip_nvidia removal. Also, the renaming part is only true for sycl/test while many of the changes are for sycl/test-e2e. There, it's not the renaming as hip LIT feature is pre-existing and means hip backend, which is true for both hip_nvidia and hip_amd. I can only change hip_amd->hip in tests' directives after/with the removal.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I've updated this PR to only modify our tests. I think that is, essentially, what you've asked for.

@aelovikov-intel aelovikov-intel requested a review from a team as a code owner January 13, 2025 22:14
@aelovikov-intel aelovikov-intel changed the title [SYCL] Remove HIP Nvidia infrastructure support [SYCL] Remove HIP Nvidia tests/CI support Jan 13, 2025
Copy link
Contributor

@uditagarwal97 uditagarwal97 left a comment

Choose a reason for hiding this comment

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

SYCL Changes LGTM.

Copy link
Contributor

@jopperm jopperm left a comment

Choose a reason for hiding this comment

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

sycl-jit changes LGTM.

Copy link
Contributor

@AlexeySachkov AlexeySachkov left a comment

Choose a reason for hiding this comment

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

Changes to Printf tests LGTM

@aelovikov-intel aelovikov-intel merged commit 96ea8dc into intel:sycl Jan 14, 2025
16 checks passed
@aelovikov-intel aelovikov-intel deleted the remove_hip_nvidia branch January 14, 2025 17:23
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.

8 participants