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
Atm the system currently features an interpreter that walks the parse tree as it is executing code. Ideally, the system would have no memory overhead and speed penalty.
I think that the future target of ilang should be at prototyping programs that do not have latency requirements and instead want to focus on throughput and efficiency. Therefore, it would make since to allow the program to be paused for an extend duration (eg >1 minute) while the system optimizes the code. Additionally, I think the system could implement a tracing compiler using the existing interpreter implementation to gather the required information.
The text was updated successfully, but these errors were encountered:
Atm the system currently features an interpreter that walks the parse tree as it is executing code. Ideally, the system would have no memory overhead and speed penalty.
I think that the future target of ilang should be at prototyping programs that do not have latency requirements and instead want to focus on throughput and efficiency. Therefore, it would make since to allow the program to be paused for an extend duration (eg >1 minute) while the system optimizes the code. Additionally, I think the system could implement a tracing compiler using the existing interpreter implementation to gather the required information.
The text was updated successfully, but these errors were encountered: