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
Model registry
Operate
Terraform modules
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
Gesh
GHC
Commits
cea1633a
Commit
cea1633a
authored
29 years ago
by
Will Partain
Browse files
Options
Downloads
Patches
Plain Diff
[project @ 1996-01-22 19:53:46 by partain]
Minor doc fixes to SysMan.lc (WDP)
parent
da618742
Loading
Loading
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
ghc/runtime/gum/SysMan.lc
+7
-7
7 additions, 7 deletions
ghc/runtime/gum/SysMan.lc
with
7 additions
and
7 deletions
ghc/runtime/gum/SysMan.lc
+
7
−
7
View file @
cea1633a
...
...
@@ -14,11 +14,11 @@ PVM. SysMan is unusual in that it is not part of the executable
produced by ghc: it is a free-standing program that spawns PVM tasks
(logical PEs) to evaluate the program.
OK children, buckle down for some serious w
i
erdness, it works like this.
OK children, buckle down for some serious we
i
rdness, it works like this.
\begin{itemize}
\item The argument vector (argv) for SysMan has one the following 2 shapes:
@
\begin{verbatim}
-------------------------------------------------------------------------------
| SysMan path | debug flag | pvm-executable path | Num. PEs | Program Args ...|
-------------------------------------------------------------------------------
...
...
@@ -26,21 +26,21 @@ OK children, buckle down for some serious wierdness, it works like this.
-------------------------------------------------------------------
| SysMan path | pvm-executable path | Num. PEs | Program Args ... |
-------------------------------------------------------------------
@
\end{verbatim}
The "pvm-executable path" is an absolute path of where PVM stashes the
code for each PE. The arguments passed on to each PE-executable
spawned by PVM are:
@
\begin{verbatim}
-------------------------------
| Num. PEs | Program Args ... |
-------------------------------
@
\end{verbatim}
The arguments passed to the Main-thread PE-executable are
@
\begin{verbatim}
-------------------------------------------------------------------
| main flag | pvm-executable path | Num. PEs | Program Args ... |
-------------------------------------------------------------------
@
\begin{verbatim}
\item SysMan's algorithm is as follows.
\begin{itemize}
\item use PVM to spawn (nPE-1) PVM tasks
...
...
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