The `peepmatic-runtime` crate contains everything required to use a `peepmatic`-generated peephole optimizer. In short: build times and code size. If you are just using a peephole optimizer, you shouldn't need the functions to construct it from scratch from the DSL (and the implied code size and compilation time), let alone even build it at all. You should just deserialize an already-built peephole optimizer, and then use it. That's all that is contained here in this crate.
25 lines
794 B
TOML
25 lines
794 B
TOML
[package]
|
|
name = "peepmatic-runtime"
|
|
version = "0.1.0"
|
|
authors = ["Nick Fitzgerald <fitzgen@gmail.com>"]
|
|
edition = "2018"
|
|
|
|
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
|
|
|
|
[dependencies]
|
|
bincode = "1.2.1"
|
|
bumpalo = "3.2.0"
|
|
log = "0.4.8"
|
|
peepmatic-automata = { version = "0.1.0", path = "../automata", features = ["serde"] }
|
|
peepmatic-macro = { version = "0.1.0", path = "../macro" }
|
|
serde = { version = "1.0.105", features = ["derive"] }
|
|
thiserror = "1.0.15"
|
|
wast = { version = "13.0.0", optional = true }
|
|
|
|
|
|
[features]
|
|
# Enable support for a few extra methods that are required by the `peepmatic`
|
|
# crate when constructing peephole optimizers, but are not needed when simply
|
|
# using already-constructed peephole optimizers.
|
|
construct = ["wast"]
|