-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[3/3][AOT][DeviceAPI] Wire up cpacked Device API context #9501
Conversation
b08b6f3
to
e685a20
Compare
f443604
to
aff40bb
Compare
263e030
to
9bcbf27
Compare
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.
Broadly looks good!. Just one question but could do in a follow up since this is green.
Adding the same functionality for the Device API to the cpacked calling convention. The MakePackedAPI pass now implicitly uses any variable named `kDeviceContextVar` as the `resource_handle` and this is then used in the `cpacked` calling convention which always expects some form of resource_handle to be passed.
9bcbf27
to
1839fb1
Compare
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.
Thanks @Mousius . LGTM
Thanks @mbs-octoml @Mousius . This is merged now! |
* [AOT][DeviceAPI] Wire up cpacked Device API context Adding the same functionality for the Device API to the cpacked calling convention. The MakePackedAPI pass now implicitly uses any variable named `kDeviceContextVar` as the `resource_handle` and this is then used in the `cpacked` calling convention which always expects some form of resource_handle to be passed. * Document calling conventions * Remove superfluous variable
* [AOT][DeviceAPI] Wire up cpacked Device API context Adding the same functionality for the Device API to the cpacked calling convention. The MakePackedAPI pass now implicitly uses any variable named `kDeviceContextVar` as the `resource_handle` and this is then used in the `cpacked` calling convention which always expects some form of resource_handle to be passed. * Document calling conventions * Remove superfluous variable
* [AOT][DeviceAPI] Wire up cpacked Device API context Adding the same functionality for the Device API to the cpacked calling convention. The MakePackedAPI pass now implicitly uses any variable named `kDeviceContextVar` as the `resource_handle` and this is then used in the `cpacked` calling convention which always expects some form of resource_handle to be passed. * Document calling conventions * Remove superfluous variable
* [AOT][DeviceAPI] Wire up cpacked Device API context Adding the same functionality for the Device API to the cpacked calling convention. The MakePackedAPI pass now implicitly uses any variable named `kDeviceContextVar` as the `resource_handle` and this is then used in the `cpacked` calling convention which always expects some form of resource_handle to be passed. * Document calling conventions * Remove superfluous variable
* [AOT][DeviceAPI] Wire up cpacked Device API context Adding the same functionality for the Device API to the cpacked calling convention. The MakePackedAPI pass now implicitly uses any variable named `kDeviceContextVar` as the `resource_handle` and this is then used in the `cpacked` calling convention which always expects some form of resource_handle to be passed. * Document calling conventions * Remove superfluous variable
Adding the same functionality for the Device API to the cpacked calling convention. The MakePackedAPI pass now implicitly uses any variable named
kDeviceContextVar
as theresource_handle
and this is then used in thecpacked
calling convention which always expects some form of resource_handle to be passed.This is stacked on top of #9500 and #9395