Uh oh!
There was an error while loading. Please reload this page.
[2/3][AOT][DeviceAPI] Add Hooks for Activate/Deactivate/Open/Close - #9500
Conversation
fb75858 to
c88bb17CompareThis adds the relevant hooks into their starting places in the code generation. As per the [C Device API RFC](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0031-devices-api.md)
c88bb17 to
4dbe678CompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
a69a7ac to
36042e4Compare| def representative_dataset(): | ||
| for _ in range(100): | ||
| data = np.random.rand(*tuple([1, 3, 4, 3])) |
There was a problem hiding this comment.
@Mousius Could the unpack here be directly from the list? Like: ...rand(*[1, 3, 4, 3])?
There was a problem hiding this comment.
Oh, nice spot @gromero, by the same token I don't think we even need to unpack the list? This is the same as rand(1, 3, 4,3), I'll clear this up 😸
There was a problem hiding this comment.
@Mousius Hi! Yeah, I thought of that too (avoiding the unpack too), however I assumed you would like to keep it as [1, 3, 4, 3] just to be "more explicit" by keeping the dimensions written in a form as you pass later for example to tf.TensorSpec. Either way looks fine to me, just the form with "tuple" seems superfluous :)
areusch
left a comment
There was a problem hiding this comment.
@mbs-octoml can you take a look too?
areusch
commented
Nov 16, 2021
@manupa-arm can you take another look? |
manupak
commented
Nov 16, 2021
Lets follow up with any outstanding comments in 3/3. @gromero@mbs-octoml |
…pache#9500) * [AOT][DeviceAPI] Add Hooks for Activate/Deactivate/Open/Close This adds the relevant hooks into their starting places in the code generation. As per the [C Device API RFC](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0031-devices-api.md) * Standardise on `lowered_ir_mods` and correct device_hook variable name
…pache#9500) * [AOT][DeviceAPI] Add Hooks for Activate/Deactivate/Open/Close This adds the relevant hooks into their starting places in the code generation. As per the [C Device API RFC](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0031-devices-api.md) * Standardise on `lowered_ir_mods` and correct device_hook variable name
…pache#9500) * [AOT][DeviceAPI] Add Hooks for Activate/Deactivate/Open/Close This adds the relevant hooks into their starting places in the code generation. As per the [C Device API RFC](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0031-devices-api.md) * Standardise on `lowered_ir_mods` and correct device_hook variable name
…pache#9500) * [AOT][DeviceAPI] Add Hooks for Activate/Deactivate/Open/Close This adds the relevant hooks into their starting places in the code generation. As per the [C Device API RFC](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0031-devices-api.md) * Standardise on `lowered_ir_mods` and correct device_hook variable name
…pache#9500) * [AOT][DeviceAPI] Add Hooks for Activate/Deactivate/Open/Close This adds the relevant hooks into their starting places in the code generation. As per the [C Device API RFC](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0031-devices-api.md) * Standardise on `lowered_ir_mods` and correct device_hook variable name
This adds the relevant hooks into their starting places in the code generation. As per the C Device API RFC
This stacks on top of #9395