rust/tests/ui/numbers-arithmetic/saturating-float-casts.rs

// run-pass
// compile-flags:-Zmir-opt-level=0

#![feature(test, stmt_expr_attributes)]
#![deny(overflowing_literals)]

#[path = "saturating-float-casts-impl.rs"]
mod implementation;

pub fn main() {
    implementation::run();
}
Add `// run-pass` annotations to all the tests under `ui/run-pass/`. (I may have accidentally added it to some auxilliary crates as well; my emacs-macro-based methodology was pretty crude.) 2018-08-30 07:18:55 -05:00			`// run-pass`
Fixup tests to test both const-eval and runtime 2020-04-19 10:53:51 -05:00			`// compile-flags:-Zmir-opt-level=0`
Saturating casts between integers and floats (both directions). This affects regular code generation as well as constant evaluation in trans, but not the HIR constant evaluator because that one returns an error for overflowing casts and NaN-to-int casts. That error is conservatively correct and we should be careful to not accept more code in constant expressions. The changes to code generation are guarded by a new -Z flag, to be able to evaluate the performance impact. The trans constant evaluation changes are unconditional because they have no run time impact and don't affect type checking either. 2017-10-08 19:14:00 -05:00
Fix missed i128 feature gates 2018-03-17 11:46:31 -05:00			`#![feature(test, stmt_expr_attributes)]`
Saturating casts between integers and floats (both directions). This affects regular code generation as well as constant evaluation in trans, but not the HIR constant evaluator because that one returns an error for overflowing casts and NaN-to-int casts. That error is conservatively correct and we should be careful to not accept more code in constant expressions. The changes to code generation are guarded by a new -Z flag, to be able to evaluate the performance impact. The trans constant evaluation changes are unconditional because they have no run time impact and don't affect type checking either. 2017-10-08 19:14:00 -05:00			`#![deny(overflowing_literals)]`

Address review comments and add UI test 2020-06-30 14:44:44 -05:00			`#[path = "saturating-float-casts-impl.rs"]`
			`mod implementation;`
Pull in miri test cases 2020-04-18 17:43:08 -05:00
Saturating casts between integers and floats (both directions). This affects regular code generation as well as constant evaluation in trans, but not the HIR constant evaluator because that one returns an error for overflowing casts and NaN-to-int casts. That error is conservatively correct and we should be careful to not accept more code in constant expressions. The changes to code generation are guarded by a new -Z flag, to be able to evaluate the performance impact. The trans constant evaluation changes are unconditional because they have no run time impact and don't affect type checking either. 2017-10-08 19:14:00 -05:00			`pub fn main() {`
Address review comments and add UI test 2020-06-30 14:44:44 -05:00			`implementation::run();`
Saturating casts between integers and floats (both directions). This affects regular code generation as well as constant evaluation in trans, but not the HIR constant evaluator because that one returns an error for overflowing casts and NaN-to-int casts. That error is conservatively correct and we should be careful to not accept more code in constant expressions. The changes to code generation are guarded by a new -Z flag, to be able to evaluate the performance impact. The trans constant evaluation changes are unconditional because they have no run time impact and don't affect type checking either. 2017-10-08 19:14:00 -05:00			`}`