- GraalVM is split into
compiler/,espresso/,espresso-compiler-stub/,espresso-shared/,regex/,sdk/,substratevm/,sulong/,tools/,truffle/,visualizer/,vm/,wasm/, andweb-image/; each suite is managed withmx. - Read the local
AGENTS.mdorREADME.mdfor the suite you change.
- Run
mxfrom the relevant suite directory. Default to thevmsuite when no better target is obvious, for examplemx -p vm build. - Common commands:
mx build,mx clean,mx unittest,mx help, andmx help <command>. - Never run multiple
mx buildormx checkstylecommands concurrently in the same workspace. They can race on sharedmxbuildoutputs and produce misleading failures or corrupt intermediate artifacts.
- Documentation sources live under
docs/. Update the matching page for user-facing changes.
- Ensure formatting and checkstyle pass (
mx checkstyle). - Confirm tests or builds relevant to your suite succeed (
mx build, targeted tests, etc.). - Verify documentation updates are included when behavior changes.
- Flag and ask for extra permission for changes related to security (e.g., touching cryptographic code).