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

[SYCL] Fix device aspect macro header CMake dependency #17358

Merged
merged 1 commit into from
Mar 10, 2025

Conversation

npmiller
Copy link
Contributor

@npmiller npmiller commented Mar 7, 2025

Without this patch the header wasn't getting re-generated when the .def files are changed, which causes build failures on existing builds when new aspects are introduced.

Without this patch the header wasn't getting re-generated when the
`.def` files are changed, which causes build failures on existing builds
when new aspects are introduced.
@npmiller npmiller requested a review from a team as a code owner March 7, 2025 15:59
@npmiller npmiller requested a review from againull March 7, 2025 15:59
Copy link
Contributor

@againull againull left a comment

Choose a reason for hiding this comment

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

LGTM , thanks for fixing this, literally yesterday someone reached out to me facing this exact problem

@npmiller
Copy link
Contributor Author

@intel/llvm-gatekeepers this is ready to merge

Test failure is unrelated and tracked here: #17285

 Failed Tests (1):
  SYCL :: SpecConstants/2020/nested-non-packed-struct.cpp

@sarnex sarnex merged commit b9324eb into intel:sycl Mar 10, 2025
25 of 27 checks passed
adamfidel pushed a commit to reble/llvm that referenced this pull request Mar 11, 2025
Without this patch the header wasn't getting re-generated when the
`.def` files are changed, which causes build failures on existing builds
when new aspects are introduced.
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.

None yet

3 participants