[SYCL][Driver] Do not pass -fopenmp-simd to device compilations #4098
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When -fopenmp-simd is used in conjunction with -fsycl, device compilation should not be passed -fopenmp-simd. Otherwise, it leads to some common cases not being able to be compiled (such as the definition of a function with a long double parameter). This is already done for other openmp options.
mdtoguchi
reviewed
Jul 13, 2021
bader
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When -fopenmp-simd is used in conjunction with -fsycl, device
compilation should not be passed -fopenmp-simd. Otherwise, it
leads to some common cases not being able to be compiled
(such as the definition of a function with a long double parameter).
This is already done for other openmp options.