[rust-dev] Integer overflow, round -2147483648

Gregory Maxwell gmaxwell at gmail.com
Fri Jun 20 19:20:58 PDT 2014


On Wed, Jun 18, 2014 at 10:08 AM, Gábor Lehel <glaebhoerl at gmail.com> wrote:
> core facts: wrapping is bad, but checking is slow. The current consensus

On this point, has anyone tried changing the emitted code for all i32
operations to add trivial checks, hopefully in a way that llvm can
optimize out when value analysis proves them redundant, which do
something trivial update a per task counter when hit and benchmarked
servo / language benchmark game programs to try to get a sane bound on
how bad the hit is even when the programmers aren't making any effort
to avoid the overhead?


More information about the Rust-dev mailing list