Skip to content

[Driver] Remove several ESIMD-specific options #4419

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 1 commit into from
Aug 30, 2021

Conversation

DenisBakhvalov
Copy link
Contributor

Previously those two options were controling splitting SYCL and ESIMD
code in sycl-post-link and lowering ESIMD-specific constructs after
that.

If there is a mix of SYCL and ESIMD kernels in a program, and we
do NOT split and lower ESIMD code then the resulting binary will be broken.

If we only have one type of kernels (regular SYCL or ESIMD), then those
two options will have no effect.

So, users should never have a situation when they need
to disable those two options, i.e. use -fno-. Since the default should
never be overwritten, we can safely remove the options.

Previously those two options were controling splitting SYCL and ESIMD
code in sycl-post-link and lowering ESIMD-specific constructs after
that.

If there is a mix of SYCL and ESIMD kernels in a program, and we
do NOT split and lower ESIMD code then the resulting binary will be broken.

If we only have one type of kernels (regular SYCL or ESIMD), then those
two options will have no effect.

So, users should never have a situation when they need
to disable those two options, i.e. use `-fno-`. Since the default should
never be overwritten, we can safely remove the options.
Copy link
Contributor

@mdtoguchi mdtoguchi left a comment

Choose a reason for hiding this comment

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

LGTM

@bader bader merged commit 6dbefb5 into intel:sycl Aug 30, 2021
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