racket

The Racket repository

Go to file

Matthew Flatt ad98dc0ddf track import "shapes" as procedure or structure type Shape information allows the linker to check the importing module's compile-time expectation against the run-time value of its imports. The JIT, in turn, can rely on that checking to better inline structure-type predicates, etc., and to more directy call JIT-generated code across module boundaries. In addition to checking the "shape" of an import, the import's JITted vs. non-JITted state must be consistent. To prevent shifts in JIT state, the `eval-jit-enabled' parameter is now restricted in its effect to top-level bindings. original commit: `d7bf677645`	2012-10-30 13:29:28 -06:00
collects	track import "shapes" as procedure or structure type	2012-10-30 13:29:28 -06:00

Matthew Flatt ad98dc0ddf track import "shapes" as procedure or structure type

Shape information allows the linker to check the importing
module's compile-time expectation against the run-time
value of its imports. The JIT, in turn, can rely on that
checking to better inline structure-type predicates, etc.,
and to more directy call JIT-generated code across
module boundaries.

In addition to checking the "shape" of an import, the import's
JITted vs. non-JITted state must be consistent. To prevent shifts
in JIT state, the `eval-jit-enabled' parameter is now restricted
in its effect to top-level bindings.

original commit: d7bf677645

2012-10-30 13:29:28 -06:00

collects track import "shapes" as procedure or structure type 2012-10-30 13:29:28 -06:00