rust/tests/ui/expr/if/if-loop.rs

// check-pass

// This used to ICE because the "if" being unreachable was not handled correctly
fn err() {
    if loop {} {}
}

fn main() {}
compiletest: Remove `skip-codegen` 2019-06-12 10:18:32 -05:00			`// check-pass`

Fix an ICE when translating `if loop {} {}` In `if loop {} {}`, the `if` is actually unreachable, but we didn't handle that correctly and when trying to translate the `if` we tried to branch on the "return value" of the loop expression, which is not an `i1` and therefore triggered an LLVM assertion. 2015-02-19 03:49:14 -06:00			`// This used to ICE because the "if" being unreachable was not handled correctly`
			`fn err() {`
			`if loop {} {}`
			`}`

Removed `#[rustc_error]` from tests that are all `// compile-pass`. I also added `// skip-codegen` to each one, to address potential concerns that this change would otherwise slow down our test suite spending time generating code for files that are really just meant to be checks of compiler diagnostics. (However, I will say: My preference is to not use `// skip-codegen` if one can avoid it. We can use all the testing of how we drive LLVM that we can get...) (Updated post rebase.) 2018-10-31 07:08:01 -05:00			`fn main() {}`