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
16eb5dec
Commit
16eb5dec
authored
26 years ago
by
Simon Marlow
Browse files
Options
Downloads
Patches
Plain Diff
[project @ 1999-02-02 16:04:02 by simonm]
Fix a couple of out-of-date things.
parent
da407089
Loading
Loading
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
ghc/docs/users_guide/runtime_control.vsgml
+17
-31
17 additions, 31 deletions
ghc/docs/users_guide/runtime_control.vsgml
with
17 additions
and
31 deletions
ghc/docs/users_guide/runtime_control.vsgml
+
17
−
31
View file @
16eb5dec
...
...
@@ -188,21 +188,6 @@ heap size based on the current amount of live data.
%PostScript), using the @stat2resid@<nidx>stat2resid</nidx> utility in
%the GHC distribution (@ghc/utils/stat2resid@).
% <tag>@-F2s@:</tag>
% <nidx>-F2s RTS option</nidx>
%
% Forces a program compiled for generational GC to use two-space copying
% collection. The two-space collector may outperform the generational
% collector for programs which have a very low heap residency. It can
% also be used to generate a statistics file from which a basic heap
% residency profile can be produced (see Section <ref name="stat2resid -
% residency info from GC stats" id="stat2resid">).
%
% There will still be a small execution overhead imposed by the
% generational compilation as the test for old generation updates will
% still be executed (of course none will actually happen). This
% overhead is typically less than 1\%.
%
% <tag>@-j<size>@:</tag>
% <nidx>-j<size> RTS option</nidx>
% Force a major garbage collection every @<size>@ bytes. (Normally
...
...
@@ -257,11 +242,10 @@ The @<file>@ business works just like on the @-S@ RTS option (above).
``Ticky-ticky'' statistics are counts of various program actions
(updates, enters, etc.) The program must have been compiled using
@-fstg-reduction-counts@<nidx>-fstg-reduction-counts option</nidx>
(a.k.a. ``ticky-ticky profiling''), and, for it to be really useful,
linked with suitable system libraries. Not a trivial undertaking:
consult the installation guide on how to set things up for easy
``ticky-ticky'' profiling.
@-ticky@<nidx>-ticky option</nidx> (a.k.a. ``ticky-ticky profiling''),
and, for it to be really useful, linked with suitable system
libraries. Not a trivial undertaking: consult the installation guide
on how to set things up for easy ``ticky-ticky'' profiling.
<tag>@-D<num>@:</tag>
<nidx>-D RTS option</nidx>
...
...
@@ -269,17 +253,19 @@ An RTS debugging flag; varying quantities of output depending on which
bits are set in @<num>@. Only works if the RTS was compiled with the
@DEBUG@ option.
<tag>@-N@:</tag>
<nidx>-N RTS option</nidx>
Normally, the garbage collector black-holes closures which are being
evaluated, as a space-saving measure. This option turns off
blackholing. You shouldn't ever need to use it.
Historical note: this option used to be used to work around a problem
with signal handling, where a signal handler might need to evaluate
blackholed closures. Signal handlers are now run in a separate
thread, and don't suffer from this problem.
% Blackholing can't be turned off in new RTS --SDM
%
% <tag>@-N@:</tag>
% <nidx>-N RTS option</nidx>
%
% Normally, the garbage collector black-holes closures which are being
% evaluated, as a space-saving measure. This option turns off
% blackholing. You shouldn't ever need to use it.
%
% Historical note: this option used to be used to work around a problem
% with signal handling, where a signal handler might need to evaluate
% blackholed closures. Signal handlers are now run in a separate
% thread, and don't suffer from this problem.
<tag>@-Z@:</tag>
<nidx>-Z RTS option</nidx>
...
...
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