-
Notifications
You must be signed in to change notification settings - Fork 787
[SYCL] Conditionally enable diagnosing that requires integration header #5044
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
Conversation
intel#4945 introduced a new diagnostic that works correcly only if integration header is included. However it is possible that `-fsycl-is-host` flag can be used without integration header, so the diagnostic should be issued only if integration header is incuded. This patch adds new cc1 option that helps to understand that.
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.
Actually, thinking a bit more - EnableIntHeader
might be confusing here. I think we should rename this to EnableIntHeaderDiag
or something
20920a3
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.
2 nits, otherwise 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.
LGTM
Can this one be merged? It appears to be quite important for the downstream. |
/summary:run |
The tests have passed. |
#4945 introduced a new diagnostic that
works correcly only if integration header is included. However it is
possible that
-fsycl-is-host
flag can be used without integrationheader, so the diagnostic should be issued only if integration header is
incuded. This patch adds new cc1 option that helps to understand that.