-
Notifications
You must be signed in to change notification settings - Fork 770
[SYCL][Joint Matrix] Pass on address space to Load/Store #9244
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
Signed-off-by: Sidorov, Dmitry <dmitry.sidorov@intel.com>
Pass on address space information to SPIR-V Joint Matrix Load/Store intrinsics
Also removed code duplication.
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
one nit: I believe we don't support constant AS for joint matrix as well (also AFAIK this AS is being deprecated in SYCL 2020)
Discussed offline: no issues here |
As we discussed in theory constant AS to load from should be supported for Joint Matrix. |
multi_ptr.get() returns decorated pointer only when IsDecorated is either decorated::yes or decorated::legacy.
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!
Failed Tests (1): |
@YuriPlyakhin @dkhaldi
whereas before this patch it would have passed. The same happens in the nvptx64 backend with this patch #9499. Maybe I'm doing something wrong but this seems to give no option to just pass in a multi_ptr from an accessor where we don't specify whether or not it is decorated? Do we really want the requirement that passed pointers must specify whether they are decorated or not? Can there be a default constructor that is not decorated perhaps? Since the implementations do not make any use of decorated pointer it seems bad that a programmer has to now pass in a decorated pointer for the local_accessor case. Note that this is not the case for a standard accessor. Local memory usage is very important for joint_matrix so it should not be penalised in this way. Note that this issue can be fixed with:
|
Pass on address space information to SPIR-V Joint Matrix Load/Store intrinsics.
TODO: