rust/library/stdarch/crates/assert-instr-macro/Cargo.toml

[package]
name = "assert-instr-macro"
version = "0.1.0"
authors = ["Alex Crichton <alex@alexcrichton.com>"]
edition = "2024"

[lib]
proc-macro = true
test = false

[dependencies]
proc-macro2 = "1.0"
quote = "1.0"
syn = { version = "2.0", features = ["full"] }

[lints.rust]
unexpected_cfgs = {level = "warn", check-cfg = ['cfg(optimized)'] }
Add assertions correct instructions are generated This commit adds a procedural macro which can be used to test instruction generation in a lightweight way. The intention is that all functions are annotated with: #[cfg_attr(test, assert_instr(maxps))] fn foo(...) { // ... } and then during `cargo test --release` it'll assert the function `foo` does indeed generate the instruction `maxps`. This only activates tests in optimized mode to avoid debug mode inefficiencies, and it uses a literal invocation of `objdump` and some parsing to figure out what instructions are inside each function. Finally it also uses the `backtrace` crate to figure out the symbol name of the relevant function and hook that up to the output of `objdump`. I added a few assertions in the `sse` module to get some feedback, but curious what y'all think of this! 2017-09-19 14:46:00 -07:00			`[package]`
			`name = "assert-instr-macro"`
			`version = "0.1.0"`
			`authors = ["Alex Crichton <alex@alexcrichton.com>"]`
Update all crates to Rust 2024 2025-02-09 10:13:55 -08:00			`edition = "2024"`
Add assertions correct instructions are generated This commit adds a procedural macro which can be used to test instruction generation in a lightweight way. The intention is that all functions are annotated with: #[cfg_attr(test, assert_instr(maxps))] fn foo(...) { // ... } and then during `cargo test --release` it'll assert the function `foo` does indeed generate the instruction `maxps`. This only activates tests in optimized mode to avoid debug mode inefficiencies, and it uses a literal invocation of `objdump` and some parsing to figure out what instructions are inside each function. Finally it also uses the `backtrace` crate to figure out the symbol name of the relevant function and hook that up to the output of `objdump`. I added a few assertions in the `sse` module to get some feedback, but curious what y'all think of this! 2017-09-19 14:46:00 -07:00
			`[lib]`
			`proc-macro = true`
Use workspaces and fix tests * Enable a Cargo workspace for the repo * Disable tests for proc-macro crates * Move back to mounting source directory read-only * Refactor test invocation to only test one crate with `--all` 2017-11-20 14:34:44 -08:00			`test = false`
Enhance `#[assert_instr]` with constant arguments Some intrinsics need to be invoked with constant arguments to get the right instruction to get generated, so this commit enhances the `assert_instr` macro to enable this ability. Namely you pass constant arguments like: #[assert_instr(foo, a = b)] where this will assert that the intrinsic, when invoked with argument `a` equal to the value `b` and all other arguments passed from the outside, will generate the instruction `foo`. Closes #49 2017-09-26 19:03:38 -07:00
			`[dependencies]`
Update proc-macro2, syn, and quote to 1.0 2019-10-06 16:30:12 +09:00			`proc-macro2 = "1.0"`
			`quote = "1.0"`
Bump syn to 2.0 Also ensure that `assert_instr` attribute has been correctly parsed in stdarch-verify. 2023-10-03 19:33:11 +02:00			`syn = { version = "2.0", features = ["full"] }`
Change test skipping logic a little, separate feature-based and function-based skipping 2025-04-16 02:34:03 +05:30
			`[lints.rust]`
			`unexpected_cfgs = {level = "warn", check-cfg = ['cfg(optimized)'] }`