There are two main types of operations provided by instances of CompileLayer.

1. You can add / remove modules using addModule / removeModuleSet.
2. You can search for symbols using findSymbol / findSymbolIn in the previously added modules.

Abstract type representing a module in a CompileLayer.

Add a module to the CompileLayer. The SymbolResolver is used to resolve external symbols in the module.

Note: This function consumes the module passed to it and it must not be used after calling this method.

Remove a previously added module.

bracket-style wrapper around addModule and removeModule.

Note: This function consumes the module passed to it and it must not be used after calling this method.

findSymbol layer symbol exportedSymbolsOnly searches for symbol in all modules added to layer. If exportedSymbolsOnly is True only exported symbols are searched.

findSymbolIn layer handle symbol exportedSymbolsOnly searches for symbol in the context of the module represented by handle. If exportedSymbolsOnly is True only exported symbols are searched.

Specifies how external symbols in a module added to a CompielLayer should be resolved.

A mangled symbol which can be used in findSymbol. This can be created using mangleSymbol.

Mangle a symbol according to the data layout stored in the CompileLayer.

IRCompileLayer compiles modules immediately when they are added. It parametrized by a LinkingLayer which handles linking of the generated object files.

Create a new IRCompileLayer.

When the layer is no longer needed, it should be disposed using 'disposeCompileLayer.

bracket-style wrapper around newIRCompileLayer and disposeCompileLayer.

Adding a module to a CompileOnDemandLayer creates stubs for its functions definitions. When one of those stubs is called, the corresponding function body is extracted and compiled.

Create a new CompileOnDemandLayer. The partitioning function specifies which functions should be compiled when a function is called.

When the layer is no longer needed, it should be disposed using disposeCompileLayer.

bracket-style wrapper around newCompileOnDemandLayer and disposeCompileLayer.

IRTransformLayer allows transforming modules before handing off compilation to the underlying CompileLayer.

Create a new IRTransformLayer.

When the layer is no longer needed, it should be disposed using disposeCompileLayer.

bracket-style wrapper around newIRTransformLayer and disposeCompileLayer.

Dispose of a CompileLayer. This should called when the CompileLayer is not needed anymore.

After a CompileLayer has compiled the modules to object code, it passes the resulting object files to a LinkingLayer.

Bare bones implementation of a LinkingLayer.

Create a new ObjectLinkingLayer. This should be disposed using disposeLinkingLayer when it is no longer needed.

bracket-style wrapper around newObjectLinkingLayer and disposeLinkingLayer.

Dispose of a LinkingLayer.

This is used by CompileOnDemandLayer to create callback that compile functions when they are called.

Create a new JITCompileCallbackManager.

When the callback manager is no longer needed, it should be freed using disposeJITCompileCallbackManager.

Dispose of a JITCompileCallbackManager.

Execute a computation using a new JITCompileCallbackManager.

This is used by CompileOnDemandLayer to manage the stubs created for function definitions that have not yet been compiled.

Create a new IndirectStubsManagerBuilder.

When the stubs manager is no longer needed, it should be freed using disposeIndirectStubsManagerBuilder.

Dispose of an IndirectStubsManagerBuilder.

bracket-style wrapper around newIndirectStubsManagerBuilder and disposeIndirectStubsManagerBuilder.