public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit 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, 14 Nov 2023 09:55:11 +0000 [thread overview] Message-ID: <bug-111842-4-U8myVYyPt4@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 #15 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:69d69865a792a93cce2905617c53913769d0f260 commit r14-5436-g69d69865a792a93cce2905617c53913769d0f260 Author: Jonathan Wakely <jwakely@redhat.com> Date: Mon Nov 13 12:03:31 2023 +0000 c++: Link extended FP conversion pedwarns to -Wnarrowing [PR111842] Several users have been confused by the status of these warnings, which can be misunderstood as "this might not be what you want", rather than diagnostics required by the C++ standard. Add the text "ISO C++ does not allow" to make this clear. Also link them to -Wnarrowing so that they can be disabled or promoted to errors independently of other pedwarns. PR c++/111842 PR c++/112498 gcc/cp/ChangeLog: * call.cc (convert_like_internal): Use OPT_Wnarrowing for pedwarns about illformed conversions involving extended floating-point types. Clarify that ISO C++ requires these diagnostics. gcc/testsuite/ChangeLog: * g++.dg/cpp23/ext-floating16.C: New test. * g++.dg/cpp23/ext-floating17.C: New test.
next prev parent reply other threads:[~2023-11-14 9:55 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 2023-10-17 23:42 ` pinskia at gcc dot gnu.org 2023-11-14 9:55 ` cvs-commit at gcc dot gnu.org [this message] 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-U8myVYyPt4@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: linkBe 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).