[PING^3] PR 21438 : Warning about division by zero depends on lexical form

Manuel López-Ibáñez lopezibanez@gmail.com
Thu Mar 1 21:14:00 GMT 2007

On 01/03/07, Joseph S. Myers <joseph@codesourcery.com> wrote:
> On Thu, 1 Mar 2007, Manuel López-Ibáñez wrote:
> > Still pending resolution:
> > http://gcc.gnu.org/ml/gcc-patches/2007-02/msg00925.html
> I don't see what there is supposed to be here for me to resolve.  If the
> patch at <http://gcc.gnu.org/ml/gcc-patches/2007-01/msg01166.html> is
> still awaiting approval rather than withdrawn or revised it is OK.

That is what I wanted to hear. Thanks.

> The int i = int(1.0/0.0); is a C++ matter, but is not a matter of a
> division-by-zero warning; rather a matter that we should warn for
> conversion of any constant infinity or NaN to an integer type, whether
> that infinity or NaN is obtained by division by zero or by using built-in
> functions.  This should go with other warnings for out-of-range
> floating-to-integer conversions.

Hum, that is a valid point. But ignoring that particular example for a
moment, the C front-end does not warn for 1.0/0.0 and with my patch
neither for 1.0/0 while the C++ front-end warns for both. So my
question is whether I should prepare a patch for the C++ front-end to
warn for both. But, I guess that, yes, that is not for you to decide,
so I should wait for a C++ front-end maintainer to speak clearly.

I was just trying to solve the inconsistency before making it worse
with the above patch. I guess things don't work that way.



More information about the Gcc-patches mailing list