Open Abhishek-Varma opened 1 year ago
Assigning to @dcaballe for now to take a look.
I think I know where the elided IR issue is coming from. What commit was this compiled on?
I forgot to add those details here. My bad! It's same as the issue for Vulkan for the same IR.
Updated the ticket and adding it here too :-
iree-compiler 20230926.533
iree-runtime 20230926.533
commit ef280a4d65e68b554ee81e8bbafa176188032c5c (HEAD -> main, origin/main, origin/HEAD)
Author: Stella Laurenzo <stellaraccident@gmail.com>
Date: Tue Sep 26 17:40:20 2023 -0700
Integrate llvm 20230926 (#15043)
Co-authored-by: Groverkss <groverkss@gmail.com>
Co-authored-by: Jakub Kuderski <jakub@nod-labs.com>
That issue is fixed by https://github.com/openxla/iree/commit/ffd5ad4e401f2ca45611da31b47c39bbbd534ff7. Could you run this on an updated version? Not sure about the other issue, this is just the elided one.
@Abhishek-Varma can you try running again?
Hi @Groverkss @allieculp - I'll take a look at this and update the ticket accordingly. Thanks!
Any update here? @Abhishek-Varma
Hi @allieculp - I'll need time here because other higher priority tasks have come up.
If you want, we can close this ticket and reopen this if any issue arises.
I think we prefer to leave it open, @dcaballe ? @Abhishek-Varma sounds good, let us know when you get to it!
Hey @allieculp, could anybody verify that this issue is actually impacting our version of llama?
What happened?
So, for CPU backend, for llama IR following scenario takes place :-
Stage A. I first tried dumping dispatches using
-iree-hal-dump-executable-sources-to=hal_sources
but individual dispatches couldn't be compiled. I therefore resorted to using--iree-flow-break-dispatch=forward_dispatch_NUMBER_
(whereNUMBER
is the dispatch I want to break into) to bisect for a dispatch during compilation. I found thatbreaking
on dispatch_11 produces a similar result of compilation being stuck.Stage B. I used the stripped version of the IR. I put that through compilation and found with
--verify=false
switched on that we hit the following error :-I dumped the exact operand on which the above assert was taking place :-
And without
--verify=false
we hit the following issue:Steps to reproduce your issue
For the compile time issue on elided IR :-
(You may add
verify=false
as well to observe the concerned issue mentioned above)And for the runtime issue on the complete IR or dispatch 11 issue mentioned above :-
--iree-flow-break-dispatch
) :-Runtime command for both case :-
What component(s) does this issue relate to?
No response
Version information
Pip package :-
Source build's last commit :-
Additional context
No response