New ARTIQ compiler, third iteration
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
pca006132 7ee82de312 nac3core: fixed weird type inference error 8 hours ago
nac3artiq Constant Default Parameter Support (#98) 5 days ago
nac3ast fix clippy warnings 3 weeks ago
nac3core nac3core: fixed weird type inference error 8 hours ago
nac3parser typo 3 weeks ago
nac3standalone Constant Default Parameter Support (#98) 5 days ago
runkernel runkernel: improve print_int debug functions 1 week ago
.gitignore nac3embedded: basic source extraction 11 months ago
Cargo.lock nac3artiq: embed linker script, put intermediate objects in temp dir 3 weeks ago
Cargo.toml integrate nac3parser 3 weeks ago
README.md README: update 3 weeks ago
flake.lock flake: switch to nixpkgs 21.11 release 5 days ago
flake.nix flake: switch to nixpkgs 21.11 release 5 days ago
llvm-future-riscv-abi.diff llvm: switch RISC-V ABI when FPU is present 2 weeks ago
llvm-restrict-targets.diff typo 2 weeks ago

README.md

NAC3 compiler

This repository contains:

  • nac3ast: Python abstract syntax tree definition (based on RustPython).
  • nac3parser: Python parser (based on RustPython).
  • nac3core: Core compiler library, containing type-checking and code generation.
  • nac3standalone: Standalone compiler tool (core language only).
  • nac3artiq: Integration with ARTIQ and implementation of ARTIQ-specific extensions to the core language.
  • runkernel: Simple program that runs compiled ARTIQ kernels on the host and displays RTIO operations. Useful for testing without hardware.

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)