Skip to content

[SYCL][WIP-DO-NOT-MERGE] Update namespaces of oneAPI and Intel extensions #2155

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

Closed
wants to merge 16 commits into from

Conversation

jbrodman
Copy link
Contributor

This PR makes the following changes to extensions in DPC++:

  1. Extensions are now in the namespace sycl::ext
  2. General language extensions are in sycl::ext::oneapi
  3. Intel HW specific extensions are in sycl::ext::intel

@jbrodman
Copy link
Contributor Author

/summary:run

jbrodman added 4 commits July 21, 2020 17:08
Signed-off-by: James Brodman <[email protected]>
Signed-off-by: James Brodman <[email protected]>
Signed-off-by: James Brodman <[email protected]>
@MrSidims MrSidims requested a review from GarveyJoe July 23, 2020 07:58
@MrSidims
Copy link
Contributor

I'm fine with updating namespaces in general and for FPGA in particular, but would like to hear from @GarveyJoe

Copy link
Contributor

@kbobrovs kbobrovs left a comment

Choose a reason for hiding this comment

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

I think moving spec constant implementation from experimental to ext::oneapi is premature. Those APIs are known to get deprecated with SYCL 2020 and replaced with new ones.

Signed-off-by: James Brodman <[email protected]>
@GarveyJoe
Copy link
Contributor

I'm fine with updating namespaces in general and for FPGA in particular, but would like to hear from @GarveyJoe

I think this will break most of our existing tests and code samples. Can you stagger the change? I.e. initially include the functions in both namespaces to give us time to convert our code and then after a grace period remove support for the old namespace?

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.

4 participants