pan/bi: Do helper termination analysis on clauses
Unlike the dependency analysis for the skip bits which is a function of the data flow graph, the thread termination analysis is dependent on the actual sequence of instructions. As such, it must be done after scheduling to be correct in the presence of out-of-order scheduling. Furthermore it's specified in terms of clauses, not instructions. Reflecting this in our code gets a nice simplification. As a side effect this puts extra td flags on subsequent clauses, which matches the DDK's behaviour. (Maybe td is just a hint?) Signed-off-by:Alyssa Rosenzweig <alyssa@collabora.com> Part-of: <!10961>
- src/panfrost/bifrost/bi_helper_invocations.c 8 additions, 12 deletionssrc/panfrost/bifrost/bi_helper_invocations.c
- src/panfrost/bifrost/bi_pack.c 5 additions, 16 deletionssrc/panfrost/bifrost/bi_pack.c
- src/panfrost/bifrost/bi_print.c 3 additions, 0 deletionssrc/panfrost/bifrost/bi_print.c
- src/panfrost/bifrost/bi_printer.c.py 0 additions, 3 deletionssrc/panfrost/bifrost/bi_printer.c.py
- src/panfrost/bifrost/bifrost_compile.c 7 additions, 2 deletionssrc/panfrost/bifrost/bifrost_compile.c
- src/panfrost/bifrost/compiler.h 3 additions, 3 deletionssrc/panfrost/bifrost/compiler.h