public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/111842] Unable to disable conversion warning in case of _Float16
Date: Tue, 17 Oct 2023 07:35:32 +0000	[thread overview]
Message-ID: <bug-111842-4-gicKrtqYgg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111842-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #6)
> (In reply to n.deshmukh@samsung.com from comment #5)
> > The code is part of a third party library hence adding a explicit cast is
> > not possible.
> 
> Well that third party library is NOT valid C++ code ... The whole point of
> the warning (and the reason why -Wno-pedantic does not turn off the warning)
> is point that out and more over point out the code should be fixed.

That is not a reason that I have ever heard for not assigning a flag to a
warning before. I was under the impression that the principle of "All warnings
should have a flag assigned to them" held regardless of how invalid the code
they warn about is, or how badly said code should be fixed. Again, see bug
44209.

  parent reply	other threads:[~2023-10-17  7:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17  2:44 [Bug c++/111842] New: " n.deshmukh at samsung dot com
2023-10-17  2:50 ` [Bug c++/111842] " pinskia at gcc dot gnu.org
2023-10-17  2:55 ` pinskia at gcc dot gnu.org
2023-10-17  2:57 ` pinskia at gcc dot gnu.org
2023-10-17  3:41 ` egallager at gcc dot gnu.org
2023-10-17  4:18 ` n.deshmukh at samsung dot com
2023-10-17  4:30 ` pinskia at gcc dot gnu.org
2023-10-17  4:43 ` n.deshmukh at samsung dot com
2023-10-17  4:45 ` pinskia at gcc dot gnu.org
2023-10-17  4:52 ` n.deshmukh at samsung dot com
2023-10-17  7:35 ` egallager at gcc dot gnu.org [this message]
2023-10-17 15:10 ` redi at gcc dot gnu.org
2023-10-17 15:11 ` redi at gcc dot gnu.org
2023-10-17 23:35 ` n.deshmukh at samsung dot com
2023-10-17 23:42 ` pinskia at gcc dot gnu.org
2023-11-14  9:55 ` cvs-commit at gcc dot gnu.org
2023-11-14 10:16 ` xry111 at gcc dot gnu.org
2023-11-14 10:29 ` redi at gcc dot gnu.org

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-111842-4-gicKrtqYgg@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).