public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/19779] IBM 128bit long double format is not constant folded. Date: Wed, 09 Mar 2022 17:53:36 +0000 [thread overview] Message-ID: <bug-19779-4-hgQoBJP4wd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-19779-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19779 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |redi at gcc dot gnu.org --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- I think this should be rejects-valid not a missed-optimization enhancement. For C++20 we reject valid code: #include <limits> constexpr long double x = 1.0L + std::numeric_limits<long double>::epsilon(); <stdin>:1:32: error: ‘(1.0e+0l + 4.94065645841246544176568792868221e-324l)’ is not a constant expression The code reduces to: constexpr long double x = 1.0L + __LDBL_EPSILON__;
next parent reply other threads:[~2022-03-09 17:53 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-19779-4@http.gcc.gnu.org/bugzilla/> 2022-03-09 17:53 ` redi at gcc dot gnu.org [this message] 2022-03-09 18:05 ` jakub at gcc dot gnu.org 2022-03-09 18:14 ` redi at gcc dot gnu.org 2022-05-12 9:27 ` pinskia at gcc dot gnu.org 2022-11-18 9:14 ` pinskia at gcc dot gnu.org 2024-02-19 10:08 ` vital.had at gmail dot com 2024-02-19 10:12 ` jakub at gcc dot gnu.org 2024-02-19 10:13 ` pinskia at gcc dot gnu.org 2024-02-19 10:18 ` iains at gcc dot gnu.org 2024-02-19 10:32 ` jakub at gcc dot gnu.org 2024-02-19 19:11 ` vital.had at gmail dot com 2024-02-19 19:19 ` redi at gcc dot gnu.org 2024-02-19 19:21 ` jakub at gcc dot gnu.org [not found] <20050203154757.19779.pinskia@gcc.gnu.org> 2005-02-08 16:43 ` steven at gcc dot gnu dot org 2005-02-20 19:41 ` pinskia at gcc dot gnu dot 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-19779-4-hgQoBJP4wd@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).