wingo pushed a change to branch wip-tailify in repository guile. discard 5348ad921 Add tailify pass discard ae3c93b2c Add new $calli expression type. discard 171e9d6a6 Add indirect-tail-call VM instruction add 896960dad Add representations for new primcalls new a1eb526b0 Add indirect-tail-call VM instruction new 171072ec5 Add new $calli expression type. new 311c69e6f Add tailify pass new 23d4263c1 Add unify-returns pass for hoot targets; wire up hoot backend
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (5348ad921) \ N -- N -- N refs/heads/wip-tailify (23d4263c1) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 4 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: am/bootstrap.am | 1 + module/language/cps/optimize.scm | 26 +++++-- module/language/cps/unify-returns.scm | 123 ++++++++++++++++++++++++++++++++++ module/language/cps/utils.scm | 7 +- 4 files changed, 151 insertions(+), 6 deletions(-) create mode 100644 module/language/cps/unify-returns.scm