Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unloop, a trifle bizarre #1

Open
albertvanderhorst opened this issue Feb 5, 2018 · 0 comments
Open

unloop, a trifle bizarre #1

albertvanderhorst opened this issue Feb 5, 2018 · 0 comments

Comments

@albertvanderhorst
Copy link

I see an unloop in symtab-lookup. My conclusion is that it goes up two levels in the call chain.
A somewhat bizarre tail-call optimization.

You've have a very nice and portable program. With this you have triple environmental dependancy

  1. a classical usage of the return stack for call addresses
  2. the return stack is used for do loop parameters
  3. do loop parameters occupy exactly two places

I had a hard time debugging it in lina because of 3. lina has 3 places for the loop parameters

In terms of clarity you program scores 9 or 10. The unloop makes it somewhere near 4.
So my advice, just leave out this unloop .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant