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
This issue deals with code implemented in #584 and #562.
In those PRs, to probe info for has_return and type_of of subroutine declaration, subroutines are evaluated twice: once with ScratchVar arguments, and once with frame pointer arguments. Then during compilation the appropriate version of subroutine evaulator is chosen and used in code generation.
Generally speaking it would be nice to avoid having to evaluate every subroutine twice. Once way of doing that could be with something like a ProxyExpr:
The idea would be to use this as a placeholder before compilation to evaluate the subroutine, then assign the ProxyExpr to its actual value once that's known at compile time.
The text was updated successfully, but these errors were encountered:
jasonpaulos
changed the title
Improve subroutine evaluation code
Improve subroutine evaluation code (post frame pointers)
Nov 8, 2022
This issue deals with code implemented in #584 and #562.
In those PRs, to probe info for
has_return
andtype_of
of subroutine declaration, subroutines are evaluated twice: once with ScratchVar arguments, and once with frame pointer arguments. Then during compilation the appropriate version of subroutine evaulator is chosen and used in code generation.Generally speaking it would be nice to avoid having to evaluate every subroutine twice. Once way of doing that could be with something like a
ProxyExpr
:The idea would be to use this as a placeholder before compilation to evaluate the subroutine, then assign the
ProxyExpr
to its actual value once that's known at compile time.The text was updated successfully, but these errors were encountered: