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 libstdc++/102916] cmath constexpr can lead to ODR violations/incorrect results Date: Mon, 25 Oct 2021 08:35:33 +0000 [thread overview] Message-ID: <bug-102916-4-7vGNJlv8oO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102916-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102916 --- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> --- And we already have a bug report about the presence of constexpr being non-conforming. IIRC the conclusion has been "yes, but it's more useful to support this than to strictly conform".
next prev parent reply other threads:[~2021-10-25 8:35 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-24 17:27 [Bug c++/102916] New: " Darrell.Wright at gmail dot com 2021-10-24 19:24 ` [Bug c++/102916] " pinskia at gcc dot gnu.org 2021-10-24 19:57 ` Darrell.Wright at gmail dot com 2021-10-24 20:18 ` Darrell.Wright at gmail dot com 2021-10-24 20:30 ` pinskia at gcc dot gnu.org 2021-10-24 20:34 ` pinskia at gcc dot gnu.org 2021-10-24 20:41 ` [Bug libstdc++/102916] " Darrell.Wright at gmail dot com 2021-10-25 8:32 ` redi at gcc dot gnu.org 2021-10-25 8:35 ` redi at gcc dot gnu.org [this message] 2021-10-25 9:32 ` redi at gcc dot gnu.org 2021-10-25 9:34 ` redi at gcc dot gnu.org 2021-10-25 13:29 ` Darrell.Wright at gmail dot com 2022-11-30 14:52 ` redi at gcc dot gnu.org 2022-11-30 14:53 ` redi at gcc dot gnu.org 2024-05-21 3:46 ` pinskia 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-102916-4-7vGNJlv8oO@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).