forked from M-Labs/nac3
pca006132
279f47f633
Previously, we have to copy types from one unification table to another, and make the table sendable. This requires cloning (processing) the whole table 3 times per function call which is not efficient and uses more memory than required when the unification table is large. We now use a concrete type table to only copy the type we need. This reduces the overhead as we only need to process the unification table for once (when we do the function codegen), and reduces memory usage by a bit (but not noticeable when the unification table is small, i.e. the types are simple). |
||
|---|---|---|
| nac3artiq | ||
| nac3core | ||
| nac3standalone | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| README.md | ||
| flake.lock | ||
| flake.nix | ||
README.md
NAC3 compiler
This repository contains:
- nac3core: Core compiler library, containing type-checking and code generation.
- nac3artiq: Integration with ARTIQ and implementation of ARTIQ-specific extensions to the core language.
- nac3standalone: Standalone compiler tool (core language only).
The core compiler knows nothing about symbol resolution, host variables etc. nac3artiq and nac3standalone provide (implement) the symbol resolver to the core compiler for resolving the type and value for unknown symbols. The core compiler only type checks classes and functions requested by nac3artiq/nac3standalone (the API should allow the caller to specify which methods should be compiled). After type checking, the compiler analyses the set of functions/classes that are used and performs code generation.
value could be integer values, boolean values, bytes (for memcpy), function ID (full name + concrete type)