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 23:35:45 +0000 [thread overview]
Message-ID: <bug-111842-4-ZCxeQT8907@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 #13 from n.deshmukh at samsung dot com <n.deshmukh at samsung dot com> ---
(In reply to Jonathan Wakely from comment #12)
> (In reply to n.deshmukh@samsung.com from comment #5)
> > The warning is valid but I wish to suppress it like the other
> > conversion warning using -Wno flag.
>
> Why?
>
> Why not just write the code correctly? It's new code, not legacy code that
> needs to be maintained. It can't be legacy code, because it would not have
> compiled before GCC 13.
The code was still working with GCC 12.1 where the same warning was classified
as a float-conversion warning.
<source>:7:18: warning: conversion from 'double' to '_Float16' may change value
[-Wfloat-conversion]
7 | _Float16 b = a;
|
The code is part of a third party library. Ideally the code should be fixed to
avoid the warning. But until the next release of the library I wanted to
disable the warnings that we were getting in our builds.
The change in behavior from gcc12 to gcc13 prompted me to come here to check if
that was an intended change.
next prev parent reply other threads:[~2023-10-17 23: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
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 [this message]
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-ZCxeQT8907@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).