Skip to content

[SYCL][E2E] add the FP16 tests in marray_geometric #12082

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 3 commits into from
Dec 21, 2023
Merged

[SYCL][E2E] add the FP16 tests in marray_geometric #12082

merged 3 commits into from
Dec 21, 2023

Conversation

jinz2014
Copy link
Contributor

@jinz2014 jinz2014 commented Dec 5, 2023

Thank you for your review.

@jinz2014 jinz2014 requested a review from a team as a code owner December 5, 2023 17:18
@jinz2014 jinz2014 changed the title [SYCL][HIP] add the FP16 tests in marray_geometric [SYCL][HIP][E2E] add the FP16 tests in marray_geometric Dec 5, 2023
@jinz2014 jinz2014 changed the title [SYCL][HIP][E2E] add the FP16 tests in marray_geometric [SYCL][E2E] add the FP16 tests in marray_geometric Dec 5, 2023
Copy link
Contributor

@cperkinsintel cperkinsintel left a comment

Choose a reason for hiding this comment

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

I haven't seen the test results complete yet, but this looks good.

@jinz2014
Copy link
Contributor Author

jinz2014 commented Dec 5, 2023

I haven't seen the test results complete yet, but this looks good.

could you please explain "test results not complete yet" ?

@cperkinsintel
Copy link
Contributor

@jinz2014 - sure. I simply meant that the CI had not yet run all the tests (including your updated one). So my approval is conditional on the tests passing ( and I don't expect any problem on that front)

@jinz2014
Copy link
Contributor Author

jinz2014 commented Dec 6, 2023

The compiler errors are the same as those reported in #12058

@KseniyaTikhomirova
Copy link
Contributor

@jinz2014 hi, tests are failing for all platforms even with -fpreview-breaking-changes flag. Could you please take a look?

@jinz2014
Copy link
Contributor Author

jinz2014 commented Dec 8, 2023

@KseniyaTikhomirova Could you please point out where the flag is added for the AMD HIP build ?

Reference #11929

@KseniyaTikhomirova
Copy link
Contributor

@KseniyaTikhomirova Could you please point out where the flag is added for the AMD HIP build ?

Reference #11929

@jinz2014 hi, I would start from test run on OCL/L0 on our HW. It is also failing. I guess the problem could be that your have lines 1-2 not removed/unchanged, with no any flags, and sycl::cross for sycl::half is still involved in compilation.

@jinz2014
Copy link
Contributor Author

@KseniyaTikhomirova Could you please point out where the flag is added for the AMD HIP build ?
Reference #11929

@jinz2014 hi, I would start from test run on OCL/L0 on our HW. It is also failing. I guess the problem could be that your have lines 1-2 not removed/unchanged, with no any flags, and sycl::cross for sycl::half is still involved in compilation.

I deleted the first two lines. Thanks.

@KseniyaTikhomirova
Copy link
Contributor

@KseniyaTikhomirova Could you please point out where the flag is added for the AMD HIP build ?
Reference #11929

@jinz2014 hi, I would start from test run on OCL/L0 on our HW. It is also failing. I guess the problem could be that your have lines 1-2 not removed/unchanged, with no any flags, and sycl::cross for sycl::half is still involved in compilation.

I deleted the first two lines. Thanks.

I clarified more details about that.
I would suggest to keep that lines to not reduce coverage. You can use __INTEL_PREVIEW_BREAKING_CHANGES define to wrap the code you added, the code that needs -fpreview-breaking-changes to be enabled to fix complication failures for initial scenario and properly add yours.

@jinz2014
Copy link
Contributor Author

@KseniyaTikhomirova Could you please point out where the flag is added for the AMD HIP build ?
Reference #11929

@jinz2014 hi, I would start from test run on OCL/L0 on our HW. It is also failing. I guess the problem could be that your have lines 1-2 not removed/unchanged, with no any flags, and sycl::cross for sycl::half is still involved in compilation.

I deleted the first two lines. Thanks.

I clarified more details about that. I would suggest to keep that lines to not reduce coverage. You can use __INTEL_PREVIEW_BREAKING_CHANGES define to wrap the code you added, the code that needs -fpreview-breaking-changes to be enabled to fix complication failures for initial scenario and properly add yours.

Thanks for the suggestions.

@againull againull merged commit d55067f into intel:sycl Dec 21, 2023
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