public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "make_all@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/101649] -Wdouble-promotion warning emitted when floating point literals are not actually promoted to doubles
Date: Mon, 02 Aug 2021 17:03:21 +0000	[thread overview]
Message-ID: <bug-101649-4-bGIWwzOdte@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101649-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101649

--- Comment #6 from South Window <make_all@t-online.de> ---
Not doing this optimization in -O0 would still leave this warning wrong when
optimization is turned on. In my view, the fundamental difference between a
generic linter and compiler warnings is that the compiler warning should
reflect what the compiler is really doing.

If it is not easy to not emit this warning, could it be possible to undo this
warning from "elsewhere", or at least to accompany this warning with a
withdrawal, e.g.


warning: implicit conversion from 'float' to 'double' to match other operand of
binary expression [-Wdouble-promotion]
warning withdrawn: literal '0.5' can be represented without loss of precision
as 'float'. Therefore, 'float' precision is used instead of 'double'.
[-Wdouble-promotion]

  parent reply	other threads:[~2021-08-02 17:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27 18:38 [Bug c++/101649] New: " make_all@t-online.de
2021-07-27 18:42 ` [Bug c++/101649] " mpolacek at gcc dot gnu.org
2021-07-27 19:18 ` make_all@t-online.de
2021-07-27 19:29 ` pinskia at gcc dot gnu.org
2021-07-27 19:54 ` make_all@t-online.de
2021-07-28  6:33 ` rguenth at gcc dot gnu.org
2021-08-02 17:03 ` make_all@t-online.de [this message]
2021-08-02 17:21 ` make_all@t-online.de

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=bug-101649-4-bGIWwzOdte@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).