Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
cmucl
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Carl Shapiro
cmucl
Commits
432febac
Commit
432febac
authored
31 years ago
by
ram
Browse files
Options
Downloads
Patches
Plain Diff
Factored out set-tail-local-call-successor into a separate function
so that the byte compiler can call it too.
parent
14091f20
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
compiler/ltn.lisp
+24
-14
24 additions, 14 deletions
compiler/ltn.lisp
with
24 additions
and
14 deletions
compiler/ltn.lisp
+
24
−
14
View file @
432febac
...
...
@@ -7,7 +7,7 @@
;;; Scott Fahlman or slisp-group@cs.cmu.edu.
;;;
(
ext:file-comment
"$Header: /Volumes/share2/src/cmucl/cvs2git/cvsroot/src/compiler/ltn.lisp,v 1.3
4
199
2/12/16 13:32:33 wlott
Exp $"
)
"$Header: /Volumes/share2/src/cmucl/cvs2git/cvsroot/src/compiler/ltn.lisp,v 1.3
5
199
3/05/08 00:45:03 ram
Exp $"
)
;;;
;;; **********************************************************************
;;;
...
...
@@ -442,11 +442,8 @@
;;; LTN-Analyze-Local-Call -- Internal
;;;
;;; Annotate the arguments as ordinary single-value continuations. If the
;;; call is a tail call, make sure that is linked directly to the bind node.
;;; Usually it will be, but calls from XEPs and calls that might have needed a
;;; cleanup after them won't have been swung over yet, since we weren't sure
;;; they would really be TR until now.
;;; Annotate the arguments as ordinary single-value continuations. And check
;;; the successor.
;;;
(
defun
ltn-analyze-local-call
(
call
policy
)
(
declare
(
type
combination
call
)
...
...
@@ -458,14 +455,27 @@
(
annotate-ordinary-continuation
arg
policy
)))
(
when
(
node-tail-p
call
)
(
let
((
caller
(
node-home-lambda
call
))
(
callee
(
combination-lambda
call
)))
(
assert
(
eq
(
lambda-tail-set
caller
)
(
lambda-tail-set
(
lambda-home
callee
))))
(
node-ends-block
call
)
(
let
((
block
(
node-block
call
)))
(
unlink-blocks
block
(
first
(
block-succ
block
)))
(
link-blocks
block
(
node-block
(
lambda-bind
callee
))))))
(
set-tail-local-call-successor
call
))
(
undefined-value
))
;;; SET-TAIL-LOCAL-CALL-SUCCESSOR -- Interface
;;;
;;; Make sure that a tail local call is linked directly to the bind
;;; node. Usually it will be, but calls from XEPs and calls that might have
;;; needed a cleanup after them won't have been swung over yet, since we
;;; weren't sure they would really be TR until now. Also called by byte
;;; compiler.
;;;
(
defun
set-tail-local-call-successor
(
call
)
(
let
((
caller
(
node-home-lambda
call
))
(
callee
(
combination-lambda
call
)))
(
assert
(
eq
(
lambda-tail-set
caller
)
(
lambda-tail-set
(
lambda-home
callee
))))
(
node-ends-block
call
)
(
let
((
block
(
node-block
call
)))
(
unlink-blocks
block
(
first
(
block-succ
block
)))
(
link-blocks
block
(
node-block
(
lambda-bind
callee
)))))
(
undefined-value
))
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment