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.

Sign up for GitHub

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

Jump to bottom

Remove unnecessary jumps in labLang #131

Closed
xrchz opened this issue Jul 27, 2016 · 3 comments
Closed

Remove unnecessary jumps in labLang #131

xrchz opened this issue Jul 27, 2016 · 3 comments
Labels
help wanted

Comments

@xrchz
Copy link
Member

xrchz commented Jul 27, 2016

Currently, compilation into labLang produces places where an unconditional jump jumps to the next instruction. Such jumps should be rewritten to Skip (which gets deleted by lab_filter) .
@xrchz xrchz mentioned this issue Jul 27, 2016
Open
@xrchz
Copy link
Member Author

xrchz commented Aug 3, 2016

I believe @cmr is working on this.

myreen added a commit that referenced this issue Aug 4, 2016
@myreen
Make clos_to_bvl sort the code-table entries
ba6686e 
The sorting ensures that code for a closure appears
immediately before any clos_call entry for the body
of the closure. The hope is that this will mean that
the tail-call from the code table entry in the closure
can in most cases be optimised to a Skip in LabLang
and then removed (see #131).
@xrchz
Copy link
Member Author

xrchz commented Dec 13, 2016

@cmr no longer working on this; I might take over when I find some time.

@xrchz xrchz self-assigned this Dec 13, 2016
xrchz added a commit that referenced this issue Dec 23, 2016
@xrchz
Prove lab_simp correct
b530355 
Progress on #131 - just need to integrate into rest of compiler.
@xrchz xrchz removed their assignment Nov 23, 2018
@tanyongkiam
Copy link
Contributor

This is superseded by #1080

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@xrchz @tanyongkiam