Commit graph

5 commits

Author SHA1 Message Date
Andrew Gallant
84331e7afb ci: limit CI to master
This prevents duplicating CI on every PR.
2017-09-27 11:04:23 -04:00
Alex Crichton
9413ec01a7 Don't backtrace failures on windows 2017-09-26 20:03:01 -07:00
Alex Crichton
f1f513d461 Fix Windows MSVC CI
Pass the `/OPT:NOICF` flag to the linker to ensure that all functions don't get
eliminated (somethign we don't want in this scenario)
2017-09-21 09:24:15 -07:00
gnzlbg
868399bcc4 [appveyor] enable panic backtraces 2017-09-21 13:49:03 +02:00
Alex Crichton
ba7f62715a 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-20 09:57:43 -07:00