Internals of JET.jl
Abstract Interpretation Based Analysis
JET.jl overloads functions with the Core.Compiler.AbstractInterpreter interface, and customizes its abstract interpretation routine. The overloads are done on JETInterpreter <: AbstractInterpreter so that typeinf(::JETInterpreter, ::InferenceState) will do the customized abstract interpretation and collect type errors.
Most overloads use the invoke reflection, which allows JETInterpreter to dispatch to the original AbstractInterpreter's abstract interpretation methods and still keep passing it to the subsequent (maybe overloaded) callees (see JET.@invoke macro).
Core.Compiler.bail_out_toplevel_call — Functionbail_out_toplevel_call(interp::JETInterpreter, ...)An overload for abstract_call_gf_by_type(interp::JETInterpreter, ...), which keeps inference on non-concrete call sites in a toplevel frame created by virtual_process.
Core.Compiler.bail_out_call — Functionbail_out_call(interp::JETInterpreter, ...)With this overload, abstract_call_gf_by_type(interp::JETInterpreter, ...) doesn't bail out inference even after the current return type grows up to Any and collects as much error points as possible. Of course this slows down inference performance, but hoopefully it stays to be "practical" speed since the number of matching methods are limited beforehand.
Core.Compiler.add_call_backedges! — Functionadd_call_backedges!(interp::JETInterpreter, ...)An overload for abstract_call_gf_by_type(interp::JETInterpreter, ...), which always add backedges (even if a new method can't refine the return type grew up to Any). This is because a new method definition always has a potential to change the JET analysis result.
Core.Compiler.const_prop_entry_heuristic — Functionconst_prop_entry_heuristic(interp::JETInterpreter, @nospecialize(rettype), sv::InferenceState, edgecycle::Bool)An overload for abstract_call_method_with_const_args(interp::JETInterpreter, ...), which forces constant prop' even if the inference result can't be improved anymore, e.g. when rettype is already Const; this is because constant prop' can still produce more accurate analysis by throwing away false positive error reports by cutting off the unreachable control flow.
JET.analyze_task_parallel_code! — Functionanalyze_task_parallel_code!(interp::JETInterpreter, @nospecialize(f), argtypes::Vector{Any}, sv::InferenceState)Adds special cased analysis pass for task parallelism (xref: https://github.com/aviatesk/JET.jl/issues/114). In Julia's task parallelism implementation, parallel code is represented as closure and it's wrapped in a Task object. NativeInterpreter doesn't run type inference nor optimization on the body of those closures when compiling code that creates parallel tasks, but JET will try to run additional analysis pass by recurring into the closures.
JET won't do anything other than doing JET analysis, e.g. won't annotate return type of wrapped code block in order to not confuse the original AbstractInterpreter routine track https://github.com/JuliaLang/julia/pull/39773 for the changes in native abstract interpretation routine.
JET.is_from_same_frame — Functionis_from_same_frame(parent_linfo::MethodInstance, current_linfo::MethodInstance) ->
(report::InferenceErrorReport) -> BoolReturns a function that checks if a given InferenceErrorReport is generated from current_linfo. It also checks current_linfo is a "lineage" of parent_linfo (i.e. entered from it).
This function is supposed to be used to filter out reports from analysis on current_linfo without using constants when entering into the constant analysis. As such, this function assumes that when a report should be filtered out, the first elment of its virtual stack frame st is for parent_linfo and the second element of that is for current_linfo.
Example: Assume linfo2 will produce a report for some reason. In the example analysis below, report2 will be filtered out on re-entering into linfo3 with constants (i.e. linfo3′). Note that report1 is still kept there because of the lineage check.
entry
└─ linfo1
├─ linfo2 (report1: linfo2)
├─ linfo3 (report1: linfo1->linfo2, report2: linfo3->linfo2)
│ └─ linfo2 (report1: linfo2, report2: linfo2)
└─ linfo3′ (report1: linfo1->linfo2, ~~report2: linfo1->linfo3->linfo2~~)JET.AbstractGlobal — Typemutable struct AbstractGlobal
t::Any # analyzed type
iscd::Bool # whether this abstract global variable is declarared as constant or not
endWraps a global variable whose type is analyzed by abtract interpretation. AbstractGlobal object will be actually evaluated into the context module, and a later analysis may refer to its type or alter it on another assignment.
The type of the wrapped global variable will be propagated only when in a toplevel frame, and thus we don't care about the analysis cache invalidation on a refinement of the wrapped global variable, since JET doesn't cache the toplevel frame.
Top-level Analysis
JET.virtual_process — Functionvirtual_process(s::AbstractString,
filename::AbstractString,
actualmod::Module,
interp::JETInterpreter,
config::ToplevelConfig,
virtualmod::Module,
) -> res::VirtualProcessResultSimulates Julia's toplevel execution and collects error points, and finally returns res::VirtualProcessResult
res.included_files::Set{String}: files that have been analyzedres.toplevel_error_reports::Vector{ToplevelErrorReport}: toplevel errors found during the text parsing or partial (actual) interpretation; these reports are "critical" and should have precedence overinference_error_reportsres.inference_error_reports::Vector{InferenceErrorReport}: possible error reports found byJETInterpreterres.toplevel_signatures: signatures of methods defined within the analyzed filesres.actual2virtual::Pair{Module, Module}: keeps actual and virtual module
This function first parses s::AbstractString into toplevelex::Expr and then iterate the following steps on each code block (blk) of toplevelex:
- if
blkis a:moduleexpression, recusively enters analysis into an newly defined virtual module lowersblkinto:thunkexpressionlwr(macros are also expanded in this step)- replaces self-references of the original root module (i.e.
actualmod) with that ofvirtualmod: seefix_self_references ConcreteInterpreterpartially interprets some statements inlwrthat should not be abstracted away (e.g. a:methoddefinition); see alsopartially_interpret!- finally,
JETInterpreteranalyzes the remaining statements by abstract interpretation
In order to process the toplevel code sequentially as Julia runtime does, virtual_process splits the entire code, and then iterate a simulation process on each code block. With this approach, we can't track the inter-code-block level dependencies, and so a partial interpretation of toplevle definitions will fail if it needs an access to global variables defined in other code blocks that are not interpreted but just abstracted. We can circumvent this issue using JET's concretization_patterns configuration, which allows us to customize JET's concretization strategy. See ToplevelConfig for more details.
JET.ConcreteInterpreter — TypeConcreteInterpreterThe trait to inject code into JuliaInterpreter's interpretation process; JET.jl overloads:
JuliaInterpreter.step_expr!to add error report pass for module usage expressions and support package analysisJuliaInterpreter.evaluate_call_recurse!to special caseincludecallsJuliaInterpreter.handle_errto wrap an error happened during interpretation intoActualErrorWrapped
JET.partially_interpret! — Functionpartially_interpret!(interp::ConcreteInterpreter, mod::Module, src::CodeInfo)Partially interprets statements in src using JuliaInterpreter.jl:
- concretizes "toplevel definitions", i.e.
:method,:struct_type,:abstract_typeand:primitive_typeexpressions and their dependencies - concretizes user-specified toplevel code (see
ToplevelConfig) - directly evaluates module usage expressions and report error of invalid module usages (TODO: enter into the loaded module and keep JET analysis)
- special-cases
includecalls so that top-level analysis recursively enters the included file
Utilities
JET.@invoke — Macro@invoke f(arg::T, ...; kwargs...)Provides a convenient way to call invoke; @invoke f(arg1::T1, arg2::T2; kwargs...) will be expanded into invoke(f, Tuple{T1,T2}, arg1, arg2; kwargs...). When an argument's type annotation is omitted, it's specified as Any argument, e.g. @invoke f(arg1::T, arg2) will be expanded into invoke(f, Tuple{T,Any}, arg1, arg2).
This could be used to call down to NativeInterpreter's abstract interpretation method of f while passing JETInterpreter so that subsequent calls of abstract interpretation functions overloaded against JETInterpreter can be called from the native method of f; e.g. calls down to NativeInterpreter's abstract_call_gf_by_type method:
@invoke abstract_call_gf_by_type(interp::AbstractInterpreter, f, argtypes::Vector{Any}, atype, sv::InferenceState,
max_methods::Int)JET.@invokelatest — Macro@invokelatest f(args...; kwargs...)Provides a convenient way to call Base.invokelatest. @invokelatest f(args...; kwargs...) will simply be expanded into Base.invokelatest(f, args...; kwargs...).
JET.@withmixedhash — Macro@withmixedhash (mutable) struct T
fields ...
endDefines struct T while automatically defining its Base.hash(::T, ::UInt) method which mixes hashes of all of T's fields (and also corresponding Base.:(==)(::T, ::T) method).
This macro is supposed to abstract the following kind of pattern:
https://github.com/aviatesk/julia/blob/999973df2850d6b2e0bd4bcf03ef90a14217b63c/base/pkgid.jl#L3-L25
struct PkgId
uuid::Union{UUID,Nothing}
name::String
end
==(a::PkgId, b::PkgId) = a.uuid == b.uuid && a.name == b.name
function hash(pkg::PkgId, h::UInt)
h += 0xc9f248583a0ca36c % UInt
h = hash(pkg.uuid, h)
h = hash(pkg.name, h)
return h
endwith
@withmixedhash
@withmixedhash struct PkgId
uuid::Union{UUID,Nothing}
name::String
endSee also: EGAL_TYPES
JET.@jetconfigurable — Macro@jetconfigurable function config_func(args...; configurations...)
...
endThis macro asserts that there's no configuration naming conflict across the @jetconfigurable functions so that a configuration for a @jetconfigurable function doesn't affect the other @jetconfigurable functions. This macro also adds a dummy splat keyword arguments (jetconfigs...) to the function definition so that any configuration of other @jetconfigurable functions can be passed on to it.