PoolTrivGrey knows that a white seg is an all-white seg, and
therefore needs no greying.
Copied from Perforce
Change: 162946
ServerID: perforce.ravenbrook.com
trace.c: traceFindGrey_diag: wrap calls in DIAG(), prevent report
overflow, reduce report array to 20 chars, and use WriteF.
Copied from Perforce
Change: 162937
ServerID: perforce.ravenbrook.com
traceFindGrey_diag() function (preparatory to leaving it in when
integrating to master).
Copied from Perforce
Change: 162676
ServerID: perforce.ravenbrook.com
Represent runs of the same rank as "Rx" where R is rank and x is
0..9, a..z (x10), or *. This makes output smaller.
Accumulate report, and only output at end of trace.
Represent "no more grey segs" as ".".
Copied from Perforce
Change: 162644
ServerID: perforce.ravenbrook.com
Show that after finding one RankFINAL segment, traceFindGrey then
goes back to RankEXACT segs before tracing the next RankFINAL segment.
Copied from Perforce
Change: 162626
ServerID: perforce.ravenbrook.com
Switch from DIAG_WITH_PRINTF to _WITH_STREAM_WRITEF.
(Still just from TraceStart).
Copied from Perforce
Change: 162395
ServerID: perforce.ravenbrook.com
trace started. This is just to test the DIAG-out mechanism; it
only affects variety.di.
Copied from Perforce
Change: 162389
ServerID: perforce.ravenbrook.com
Hope to fix in time, but for now I need DIAG-out to work, so switch
to printf (yes, really, I know, sorry).
Also, only do DIAG-out in variety.di, to avoid damage to .ci.
So for now, remove DIAG_WRITEF and DIAG from arenavm and trace.
To test, add DIAG_PRINTF in trace.
Copied from Perforce
Change: 162387
ServerID: perforce.ravenbrook.com
Also: DIAG-out TraceStart reason, and -- if a non-monor collection --
DIAG-out an ArenaDescribe.
Copied from Perforce
Change: 162213
ServerID: perforce.ravenbrook.com
(plus some edits: integrations were not not verbatim)
poolamc.c: Count the loops of amcScanNailed.
If amcScanNailed looped, ss.unfixedSummary is
not accurate, so move all of the ScanStateSummary into
ss.fixedSumamry, so that trace.c's .verify.segsummary
does not erroneously fail.
This fixes job001548.
trace.c: (comment) explain .verify.segsummary
poolamc.c: AMCSegSketch: four character sketch of seg-state
Copied from Perforce
Change: 162150
ServerID: perforce.ravenbrook.com
not accurate, so move all of the ScanStateSummary into ss.fixedSumamry,
so that <impl/trace/#verify.segsummary> does not erroneously fail.
See also log file a2nNailedLoopReset.txt.
Copied from Perforce
Change: 162000
ServerID: perforce.ravenbrook.com
shows summary is CORRECT. So: discrepancy between refs seen by
AMCSegAllobjSummary() and those seen by AMCScan() of boarded segment.
Copied from Perforce
Change: 161996
ServerID: perforce.ravenbrook.com
Save sketches (abzSketchTotal and abzSketchTotalPrev) in amcseg,
which get Described when unfixedSummary is wrong: let's see whether
there's a pattern to the way the previous summary was created.
Copied from Perforce
Change: 161994
ServerID: perforce.ravenbrook.com
SegDescribe the seg being scanned, and the seg being Fixed (ie. holding
the referent object that we have just failed to forward).
Copied from Perforce
Change: 161979
ServerID: perforce.ravenbrook.com
- new mps_message_type_gc_start() explains what triggered a collection;
- design/message: add guide.
Copied from Perforce
Change: 161204
ServerID: perforce.ravenbrook.com
TraceStart may overwrite fields of in-use message.
TraceStart may silently drop the TraceStartMessage.
Copied from Perforce
Change: 161203
ServerID: perforce.ravenbrook.com
