commit ed27593a9e9a2f5a29d091dfb016ca1204075c6f
parent fafdf7c7f6c35609309c6b7bd526f79c22e31b4a
Author: Matthew Gaudet <mgaudet@mozilla.com>
Date: Wed, 1 Oct 2025 17:58:26 +0000
Bug 1991984 - Cleanup and enhance hazard docs r=sfink DONTBUILD
Differential Revision: https://phabricator.services.mozilla.com/D267058
Diffstat:
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/js/src/doc/HazardAnalysis/running.md b/js/src/doc/HazardAnalysis/running.md
@@ -26,17 +26,24 @@ To run the analysis on SpiderMonkey:
mach hazards analyze --project=js
-Output goes to `$srctop/haz-js/hazards.txt`. This will run the analysis on the js/src
-tree only; if you wish to analyze the full browser, use
+ Output goes to `$srctop/haz-js/hazards.txt`. This will run the analysis on the js/src
+ tree only; if you wish to analyze the full browser, use
--project=browser
-(or leave it off; `--project=browser` is the default)
+ (or leave it off; `--project=browser` is the default)
6. (optional) View the resulting hazards.
mach hazards view --project=js
+7. If you see any bizarre behaviours (compiler crashes, impossible situations) etc,
+ be relatively free with
+
+ mach hazards clobber
+
+ to remove potentially broken files.
+
After running the analysis once, you can reuse the `*.xdb` database files
generated, using modified analysis scripts, by running either the `mach hazards
analyze` command above, or by adding on `mach hazards analyze <step>` to
