Ben Vanik
Ben Vanik
It's not possible reliably in the compiler (if there are dynamic shapes there's nothing we can do, if the values are derived from runtime queries, etc). The HIP HAL could...
yeah, especially for stuff like this I just assume (hah) upstream doesn't support what we need in conjunction with our better type support and assume ops. really good detective work...
Agreed RE upstream analysis interaction - I think we could provide interface implementations if upstream uses them that distills the info (I don't think we do). The particular benefit of...
I don't think anyone is going to try to reproduce this given the steps provided. In cases like these you will need to capture a Tracy trace and post it....
No, all arguments are loaded on the first device. Generally arguments should be small. Are you passing giant parameters as arguments?
The way to do that today would be to have a harness module that does your setup how you want instead of relying on command line arguments. See https://github.com/google/iree/blob/16f937893cd4a8edf92bdbc4227a5ab0049373c3/samples/multiple_modules/README.md for...
that pass is fundamentally incompatible with multi-device - you need to disable data tiling
The attribute is what is referencing the symbol, not the op. We verify these later on but because this pass is running in the wrong place it happens before the...
Promises are ok - affinities are not. Promises do not need the symbol to exist. The op does not know that the affinity attribute even has a symbol. The cases...
Hold up - that's not the correct approach.