public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rlcamp.pdx at gmail 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: Wed, 17 Jan 2024 17:35:09 +0000 [thread overview]
Message-ID: <bug-48379-4-PxPYHJPyM0@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
Campbell <rlcamp.pdx at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rlcamp.pdx at gmail dot com
--- Comment #5 from Campbell <rlcamp.pdx at gmail dot com> ---
I second everything said here - this is still annoying and significantly
increases the noise level when looking for legitimate actionable warnings, when
it is not itself actionable other than by adding an explicit cast to silence
it.
prev parent reply other threads:[~2024-01-17 17:35 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
2024-01-17 17:35 ` rlcamp.pdx at gmail dot com [this message]
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-PxPYHJPyM0@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).