[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lmi] Integer overflow warnings in bourn_cast with clang
From: |
Vadim Zeitlin |
Subject: |
Re: [lmi] Integer overflow warnings in bourn_cast with clang |
Date: |
Thu, 6 Apr 2017 21:11:59 +0200 |
On Thu, 6 Apr 2017 18:35:03 +0000 Greg Chicares <address@hidden> wrote:
GC> On 2017-04-06 15:53, Vadim Zeitlin wrote:
GC> [...]
GC> > Any error messages produced due to a failure in this cast will
GC> > almost certainly be completely incomprehensible to any end user and,
GC> > hopefully, relatively clear to any developer if they include the value
GC> > being cast and the types being casted from/to (and not really useful
GC> > without them).
GC>
GC> Replying only to this part of your message for now--I've just pushed
GC> a change that clarifies the error message in the way I believe you
GC> recommended, e.g.:
GC>
GC> Cast from 3.140000 [float] to 3 [long long] would not preserve value.
This is definitely incomparably more useful, thank you!
VZ
- [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
Re: [lmi] Integer overflow warnings in bourn_cast with clang, Greg Chicares, 2017/04/12