Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
GHC
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
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
alexbiehl-gc
GHC
Commits
2fa7ebd4
Commit
2fa7ebd4
authored
27 years ago
by
Simon Marlow
Browse files
Options
Downloads
Patches
Plain Diff
[project @ 1997-09-24 16:19:53 by simonm]
finished today's changes.
parent
2bc355fa
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/rts/rts.verb
+30
-0
30 additions, 0 deletions
docs/rts/rts.verb
with
30 additions
and
0 deletions
docs/rts/rts.verb
+
30
−
0
View file @
2fa7ebd4
...
...
@@ -799,6 +799,36 @@ How do we do this?
\subsection{A GHC thread returns to a Hugs-compiled return address}
When Hugs pushes return addresses on the stack, they look like this:
@
| |
|_______________|
| | -----> bytecode object
|_______________|
| | _____
|_______________| |___ GHC-friendly return code
_____
| |
| | Info Table
|____|
. .
. . Code
. .
@
If GHC is returning, it will return to the address at the top of the
stack. The code at this address
\begin{itemize}
\item saves the thread state in the TSO
\item returns to the scheduler with a @whatNext@ field of @RunHugs@.
\end{itemize}
If Hugs is returning to one of these addresses, it can spot the
special return address at the top and instead jump to the bytecodes
pointed to by the second word on the stack.
\subsection{A Hugs thread enters a GHC-compiled thunk}
When Hugs is called on to enter a non-Hugs closure (these are
...
...
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