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
We current use threads with very large stack sizes to prevent getting a stack overflow when traversing deep ASTs. However, it would be better to change these traversals so they don't use the call-stack for going into nested code.
The test nesting.bpl triggers some traversals of deeply nested code, and without using large stacks this test fails to pass.
PR #709 is a WIP attempt at using a stack on the heap
The text was updated successfully, but these errors were encountered:
I am trying to understand the connection between the two pull requests #710 and #709 . Is #710 a temporary measure which would become unnecessary once #709 lands?
We current use threads with very large stack sizes to prevent getting a stack overflow when traversing deep ASTs. However, it would be better to change these traversals so they don't use the call-stack for going into nested code.
The test
nesting.bpl
triggers some traversals of deeply nested code, and without using large stacks this test fails to pass.PR #709 is a WIP attempt at using a stack on the heap
The text was updated successfully, but these errors were encountered: