rust/library/stdarch/crates/assert-instr-macro/build.rs

use std::env;

fn main() {
    let opt_level = env::var("OPT_LEVEL")
        .ok()
        .and_then(|s| s.parse().ok())
        .unwrap_or(0);
    let profile = env::var("PROFILE").unwrap_or_default();
    if profile == "release" || opt_level >= 2 {
        println!("cargo:rustc-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			`use std::env;`

			`fn main() {`
[ci] check formatting (#64) * [ci] check formatting * [rustfmt] reformat the whole library 2017-10-27 17:55:29 +02:00			`let opt_level = env::var("OPT_LEVEL")`
			`.ok()`
			`.and_then(\|s\| s.parse().ok())`
			`.unwrap_or(0);`
Fix some clippy lints (#937) 2020-11-01 19:53:39 -05:00			`let profile = env::var("PROFILE").unwrap_or_default();`
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			`if profile == "release" \|\| opt_level >= 2 {`
			`println!("cargo:rustc-cfg=optimized");`
			`}`
			`}`