-
Notifications
You must be signed in to change notification settings - Fork 801
[SYCL] Address multi_ptr intel/llvm vs spec mismatches. #10297
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
- Deprecation of multi_ptr ctor from accessor(Reg, Void) with target::local - ctor from accessor(Void) and local_accessor with generic_space - Deprecation of multi_ptr<legacy> - ctor(Legacy) from local_accessor - Add const qualified to explicit conversion of multi_ptr<generic_space> to multi_ptr of any other address space.
…on guide from constant_buffer specialised accessor to conform with the spec.
|
@mmoadeli Could you please fix LIT failures. |
|
Could you please merge origin/sycl branch because some of the tests failed because of misalignment between test-e2e and compiler (see #10334 for details) |
Co-authored-by: Artur Gainullin <[email protected]>
Co-authored-by: Artur Gainullin <[email protected]>
|
@mmoadeli Could you please fix the following failure: |
Could you please point me to the specification where I can see this deduction rule? |
|
|
@againull This change is not still part of spec. There is a pending PR for it |
- Deduction guide construct decorated::no specialised multi_ptr for constant_buffer specialized accessors.
- Replace deprecated access::target with target.
Fix for use of non-standard multi_ptr constructors in several Joint Matrix tests exposed by intel#10297
Fix for use of non-standard multi_ptr constructors in several Joint Matrix tests exposed by #10297
…0583) Fix for use of non-standard multi_ptr constructors in several Joint Matrix tests exposed by intel#10297
Uh oh!
There was an error while loading. Please reload this page.