Whenever it is legal to do so, CM lets multiple invocations of CM.make or CM.autoload share dynamic state created by link-time effects. Of course, sharing is not possible (and hence not ``legal'') if the compilation unit in question has recently been recompiled or depends on another compilation unit whose code has recently been re-executed. The programmer can explicitly mark certain ML files as shared, in which case CM will issue a warning whenever the unit's code has to be re-executed.
State created by compilation units marked as private is never shared across multiple calls to CM.make or CM.autoload. To understand this behavior it is useful to introduce the notion of a traversal. A traversal is the process of traversing the dependency graph on behalf of CM.make or CM.autoload. Several traversals can be executed interleaved with each other because a CM.autoload traversal normally stays suspended and is performed incrementally driven by input from the interactive top level loop.
As far as sharing is concerned, the rule is that during one traversal each compilation unit will be executed at most once. This means that the same ``program'' will not see multiple instantiations of the same compilation unit (where ``program'' refers to the code managed by one call of CM.make or CM.autoload). Each compilation unit will be linked at most once during a traversal and private state will not be confused with private state of other traversals that might be active at the same time.