public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/106652] [C++23] P1467 - Extended floating-point types and standard names Date: Fri, 09 Sep 2022 09:44:43 +0000 [thread overview] Message-ID: <bug-106652-4-yw4Vgb4xtd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106652-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106652 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #53508|0 |1 is obsolete| | --- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 53555 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53555&action=edit gcc13-pr106652-wip.patch Some further progress. Introduces a helper extended_float_type_p and uses it and attempts to implement 2) from above and add some testcase coverage for it (not complete, because right now there are just float{16,32,64,128} effective targets and not effective targets for various float/double/long double type properties (e.g. if they are ieee type), so for the cases where there should be an error on the conversion I've kept only cases where I know for sure using the above mentioned effective targets, not where it is sometimes the case and sometimes it isn't. From the above list, 1) needs decision what to do about arithmetics in that type, 4) needs discussion on where to diagnose it, 5) needs implementation.
next prev parent reply other threads:[~2022-09-09 9:44 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-16 17:14 [Bug c++/106652] New: " mpolacek at gcc dot gnu.org 2022-08-24 14:27 ` [Bug c++/106652] " jakub at gcc dot gnu.org 2022-08-24 14:49 ` jakub at gcc dot gnu.org 2022-08-24 16:56 ` jakub at gcc dot gnu.org 2022-08-24 17:35 ` joseph at codesourcery dot com 2022-08-25 12:51 ` jakub at gcc dot gnu.org 2022-08-25 12:55 ` jakub at gcc dot gnu.org 2022-08-25 14:39 ` jakub at gcc dot gnu.org 2022-09-09 9:44 ` jakub at gcc dot gnu.org [this message] 2022-09-09 18:12 ` jakub at gcc dot gnu.org 2022-09-10 10:20 ` jakub at gcc dot gnu.org 2022-09-10 10:22 ` jakub at gcc dot gnu.org 2022-09-10 17:28 ` jakub at gcc dot gnu.org 2022-09-10 17:31 ` jakub at gcc dot gnu.org 2022-09-10 18:13 ` jakub at gcc dot gnu.org 2022-09-27 6:18 ` cvs-commit at gcc dot gnu.org 2022-10-18 9:43 ` cvs-commit at gcc dot gnu.org 2022-10-19 9:26 ` cvs-commit at gcc dot gnu.org 2022-11-19 9:24 ` jakub at gcc dot gnu.org 2022-11-28 22:31 ` pinskia at gcc dot gnu.org 2022-12-09 15:20 ` pinskia at gcc dot gnu.org 2023-08-21 15:57 ` igorkuo at meta dot ua 2023-08-22 14:15 ` cvs-commit at gcc dot gnu.org 2023-08-22 14:16 ` cvs-commit 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-106652-4-yw4Vgb4xtd@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).