From: Andrea Bocci <andrea.bocci@cern.ch>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: Warn about conversion from floating point to integers
Date: Mon, 22 Aug 2022 21:27:09 +0200 [thread overview]
Message-ID: <CAAK6D=6j0J2B1zzCU9z3mBvv_OUctOSOhHQc3Eu=Lnugd3-K=w@mail.gmail.com> (raw)
In-Reply-To: <20220822173203.GP25951@gate.crashing.org>
On Mon, 22 Aug 2022 at 19:33, Segher Boessenkool <segher@kernel.crashing.org>
wrote:
> Hi!
>
> On Sat, Aug 20, 2022 at 11:21:50AM +0200, Andrea Bocci wrote:
> > is there a way to ask GCC to produce a warning when there is a conversion
> > from a floating point type (float or double) to an integer type (char,
> > short, int, long, etc.), but not when there is a conversion from double
> to
> > float ?
> >
> > The reason is that we often do computations in double precision and store
> > the result in single precision, so I'd rather not warn about that.
> >
> > -Wconversion warns about both kinds and more.
> > -Wfloat-conversion warns about both kinds.
>
> There is no separate option. But, you can just grep the error messages?
>
> fc.c: In function 'f':
> fc.c:1:28: warning: conversion from 'double' to 'float' may change value
> [-Wfloat-conversion]
> 1 | float f(double x) { return x; }
> | ^
> fc.c: In function 'g':
> fc.c:2:26: warning: conversion from 'double' to 'int' may change value
> [-Wfloat-conversion]
> 2 | int g(double x) { return x; }
> | ^
>
> Not ideal of course, but this should be workable? (You may want to set
> LANG=C to get parsable warning messages).
>
> If you want a separate -W option for this, please file a PR?
> See <https://gcc.gnu.org/bugs.html>. Thanks!
>
Hi Segher,
thank you for your message !
From a test build of our code base with -Wfloat-conversion we got over 700k
warnings from 65k unique locations, the vast majority being about "warning:
conversion from 'double' to 'float' may change value".
So, while we can run an ad-hoc build with -Wfloat-conversion and
post-process the compiler messages, it's not something we can really keep
enabled all the time.
Making a PR for this might be a tad complicated, but I agree it would be
the best way forward... so thanks for the suggestion :-)
Ciao,
.Andrea
--
Dr. Andrea Bocci
Applied Physicist, CMS Experiment
<https://cms.cern/>EP-CMD, CERN
<https://home.cern/>168990 (+41 75 411 8990)
CERN 40/1-B01 <https://maps.cern.ch/mapsearch/mapsearch.htm?n=['40/1-B01']>
E27810
Esplanade des particules, 1, CH-1211 Geneve 23, Switzerland
<https://goo.gl/maps/AMjHdhXzYk2itSu7A>
next prev parent reply other threads:[~2022-08-22 19:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 9:21 Andrea Bocci
2022-08-22 17:32 ` Segher Boessenkool
2022-08-22 19:27 ` Andrea Bocci [this message]
2022-08-22 19:43 ` Jonathan Wakely
2022-08-22 19:48 ` Andrea Bocci
2022-08-22 23:01 ` Segher Boessenkool
2022-08-22 23:39 ` Jeff Law
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAK6D=6j0J2B1zzCU9z3mBvv_OUctOSOhHQc3Eu=Lnugd3-K=w@mail.gmail.com' \
--to=andrea.bocci@cern.ch \
--cc=gcc-help@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).