You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setup code should *always* be emitted before emitting of the own computation
code, e.g. the setup code must be emitted before compiling a data layout since
this compilation may temporarily introduce boolean variables and emit code
using them into the returned blocks, however, these blocks may be placed
between setup and teardown code which may represent the lifespan of another
boolean variable which then overrides the value of the other one (our DSL is
able to use the same bit again since the `Variable` object is already distroyed
and thus its bit is free to use).
We had this issue previously and thus introduced the `referenced_bits_` field
for `PrimitiveExpr`s, however, beeing able to return blocks of Wasm code and
place them somewhere else circumvents our former solution. Maybe we can extend
the idea of memorizing referenced bits to blocks as well until they are
attached or destroyed.
0 commit comments