Javascript:Hazard Builds: Difference between revisions

Only talk about hazard builds
(→‎Running the analysis: Updated instructions to something that'll actually work)
(Only talk about hazard builds)
Line 1: Line 1:
== Goal ==
== Static Analysis for Rooting Hazards ==
 
The goal of this project is to know the exact locations of all GC Cell pointers stored on the stack.  This will enable further development of compacting and generational GC modes.
 
== Dynamic Rooting Analysis ==
 
Since a failure to root a stack variable properly will become a use-after-free error after we have moving GC's, it is vitally important that we catch and fix all rooting violations now, rather than later.  To this end, we have enabled a dynamic correctness checker that runs on every push to mozilla-inbound.  It verifies that no stack pointers are left unrooted.  It is displayed on Treeherder under the name SM(r).
 
== Static Rooting Analysis ==


Treeherder can run three static analysis builds: the full browser (linux64-br-haz), B2G (linux64-b2g-haz), and just the JS shell (linux64-sh-haz). They show up on treeherder as '''H''' (or '''SM(H)''').
Treeherder can run three static analysis builds: the full browser (linux64-br-haz), B2G (linux64-b2g-haz), and just the JS shell (linux64-sh-haz). They show up on treeherder as '''H''' (or '''SM(H)''').
Confirmed users
328

edits