diff options
| author | bors <bors@rust-lang.org> | 2018-03-30 14:11:35 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2018-03-30 14:11:35 +0000 |
| commit | a6f1c6a3eee2c09e99935083665e5d034871a0e4 (patch) | |
| tree | 92b7d58d90ec720f41d4f17170c94d396fbb2564 /src/rustllvm/RustWrapper.cpp | |
| parent | 4379c86fe752d0e2eb969646d5a18014ac969a26 (diff) | |
| parent | 38d48ef53778674baa99dd0a3a193cec78f74e63 (diff) | |
| download | rust-a6f1c6a3eee2c09e99935083665e5d034871a0e4.tar.gz rust-a6f1c6a3eee2c09e99935083665e5d034871a0e4.zip | |
Auto merge of #49425 - alexcrichton:disallow-inline-always, r=petrochenkov
rustc: Forbid #[inline(always)] with #[target_feature] Once a target feature is enabled for a function that means that it in general can't be inlined into other functions which don't have that target feature enabled. This can cause both safety and LLVM issues if we were to actually inline it, so `#[inline(always)]` both can't be respected and would be an error if we did so! Today LLVM doesn't inline functions with different `#[target_feature]` annotations, but it turns out that if one is tagged with `#[inline(always)]` it'll override this and cause scary LLVM error to arise! This commit fixes this issue by forbidding these two attributes to be used in conjunction with one another. Closes rust-lang-nursery/stdsimd#404
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions