public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "n.deshmukh at samsung dot com" <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 04:52:47 +0000 [thread overview]
Message-ID: <bug-111842-4-7CuAStXTxo@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 #9 from n.deshmukh at samsung dot com <n.deshmukh at samsung dot com> ---
(In reply to Andrew Pinski from comment #8)
> (In reply to n.deshmukh@samsung.com from comment #7)
> >
> > Is there a reason why the second error is not categorized under
> > -Wfloat-conversion diagnostic?
>
> Did you read what I linked?
> I will link it again:
> https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p1467r4.
> html#implicit
>
> It even mentions why things won't change.
> Again the code:
> ```
> float a;
> _Float16 b = a;
> ```
> is invalid C++ code as defined by that paper (which was addopted for C++23).
> While:
> ```
> double a;
> float b = a;
> ```
> is still valid even.
Yes I went through the link and I understand that double to float conversion is
valid code. My question was regarding the use of the diagnostic flag. My
understanding was that the diagnostic flag was implementation defined. That's
why I was asking.
next prev parent reply other threads:[~2023-10-17 4:52 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 [this message]
2023-10-17 7:35 ` egallager at gcc dot gnu.org
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-7CuAStXTxo@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).