[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lmi] Integer overflow warnings in bourn_cast with clang
From: |
Greg Chicares |
Subject: |
Re: [lmi] Integer overflow warnings in bourn_cast with clang |
Date: |
Thu, 6 Apr 2017 18:35:03 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.6.0 |
On 2017-04-06 15:53, Vadim Zeitlin wrote:
[...]
> Any error messages produced due to a failure in this cast will
> almost certainly be completely incomprehensible to any end user and,
> hopefully, relatively clear to any developer if they include the value
> being cast and the types being casted from/to (and not really useful
> without them).
Replying only to this part of your message for now--I've just pushed
a change that clarifies the error message in the way I believe you
recommended, e.g.:
Cast from 3.140000 [float] to 3 [long long] would not preserve value.
- [lmi] Integer overflow warnings in bourn_cast with clang, Vadim Zeitlin, 2017/04/05
- Re: [lmi] Integer overflow warnings in bourn_cast with clang, Greg Chicares, 2017/04/07
- Re: [lmi] Integer overflow warnings in bourn_cast with clang, Vadim Zeitlin, 2017/04/07
- Re: [lmi] Integer overflow warnings in bourn_cast with clang, Greg Chicares, 2017/04/09
- Re: [lmi] Integer overflow warnings in bourn_cast with clang, Vadim Zeitlin, 2017/04/09
- Re: [lmi] Integer overflow warnings in bourn_cast with clang, Greg Chicares, 2017/04/10
- Re: [lmi] Integer overflow warnings in bourn_cast with clang, Greg Chicares, 2017/04/12
- Re: [lmi] Integer overflow warnings in bourn_cast with clang, Vadim Zeitlin, 2017/04/12