-
Notifications
You must be signed in to change notification settings - Fork 756
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] Don't include iostream from sycl.hpp #11373
base: sycl
Are you sure you want to change the base?
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
l0-pi LGTM
@Alcpz, @joeatodd, @PietroGhg, @uwedolinsky, @stdale-intel: this requires a syclcompat-lib-reviewers review. Can one of you please do that? Thanks! |
I just noticed #11326. @aelovikov-intel, @steffenlarsen do I need to do the same here (include it unless SYCL2020_CONFORMANT_APIS). |
@rolandschulz yes, you will need to hide it under the macro for now, and it will be promoted during ABI breaking cycle |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the syclcompat/device.hpp change lgtm
also include headers unless SYCL2020_CONFORMANT_APIS
@KseniyaTikhomirova Do you want to review the changes since your last review? Or is this ready to merge? |
Ready to merge |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Blocking for a moment.
@rolandschulz we discussed/reviewed this internally with the architects (@gmlueck / @jbrodman / @bashbaug ) and we do not need to treat this as breaking change, and you can remove the guards if you would like and do not have reason to believe this directly breaks anything. |
Are we also removing the cmath and complex include from sycl.hpp? Otherwise this seems inconsistent. Do you want me to remove them as part of this PR? |
I'll create a separate PR for that. |
@@ -16,7 +16,7 @@ | |||
#include <layers/zel_tracing_api.h> | |||
#include <ze_api.h> | |||
|
|||
#include <sycl/detail/iostream_proxy.hpp> | |||
#include <../../source/detail/iostream_proxy.hpp> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm pretty sure this is wrong. What's the correct way to share an include between source and plugin?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no - it shouldn't be done. Includes from source aren't shipped.
@rolandschulz Could you please resolve merge conflicts. |
This pull request is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be automatically closed in 30 days. |
No description provided.