public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcrocker at eschertech dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/48379] -Wdouble-promotion warns for promotion by varargs
Date: Tue, 18 Oct 2022 14:29:32 +0000	[thread overview]
Message-ID: <bug-48379-4-HV6HIKzjqW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48379-4@http.gcc.gnu.org/bugzilla/>

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

David Crocker <dcrocker at eschertech dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dcrocker at eschertech dot com

--- Comment #4 from David Crocker <dcrocker at eschertech dot com> ---
I too am getting fed up with having to add an explicit cast to double to
suppress the warning whenever I pass a float to a varargs function. I have
probably spent a few hours this year adding these casts. As has already been
said, nothing can he done about the promotion in this context, so it's not
worth warning about. Whereas in other situations, the warning is very useful to
me because I work with embedded processors that have single-precision but not
double-precision floating point hardware, so I want to avoid double precision
maths as far as possible.

  parent reply	other threads:[~2022-10-18 14:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31  4:56 [Bug c++/48379] New: " jmuizelaar at mozilla dot com
2011-03-31 10:38 ` [Bug c++/48379] " rguenth at gcc dot gnu.org
2013-11-23 14:15 ` achurch+gcc at achurch dot org
2022-10-18 14:29 ` dcrocker at eschertech dot com [this message]
2024-01-17 17:35 ` rlcamp.pdx at gmail dot com

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-48379-4-HV6HIKzjqW@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).