News for hackers. Stuff that matters.
Re:How expensive is integer-overflow trapping in C++? by lytigas on Thursday September 24, 2020 @02:32AM (#24575893)
Rust wraps in release mode and traps in debug mode[0][1]. All large projects that I know of ship in release mode. Though I'd be interested to see a source for it not pessimizing badly.

[0] https://play.rust-lang.org/?version=stable&mode=release&edit...

[1] https://github.com/rust-lang/rfcs/pull/560

Re:How expensive is integer-overflow trapping in C++? by fluffy87 on Thursday September 24, 2020 @07:12AM (#24577409)
See my reply to masklin in this thread for why this is incorrect. In release mode, the behavior of integer overflow in Rust is not UB/cannot happen, but modulo two arithmetic.

These two are not the same thing.

Re:How expensive is integer-overflow trapping in C++? by tom_mellior on Thursday September 24, 2020 @08:18AM (#24577845)
Huh? Parent wrote:

>> Rust wraps in release mode and traps in debug mode

You wrote:

> In release mode, the behavior of integer overflow in Rust is not UB/cannot happen, but modulo two arithmetic.

The parent didn't claim or imply that overflow is UB. The parent wrote that it "wraps", which is equivalent to your "modulo two arithmetic". You are not in disagreement, so why are you disagreeing?

Re:How expensive is integer-overflow trapping in C++? by sanxiyn on Thursday September 24, 2020 @03:06AM (#24576097)
It is quite believable that trapping does not slow down Firefox. GCC is part of SPECint, and trapping is known not to slow down SPECint GCC. (It does slow down other SPECint benchmarks.)