public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kariya_mitsuru at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/61791] New: [C++11] [constexpr] Additional overloads of std::real should be a constexpr function Date: Sun, 13 Jul 2014 08:49:00 -0000 [thread overview] Message-ID: <bug-61791-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61791 Bug ID: 61791 Summary: [C++11] [constexpr] Additional overloads of std::real should be a constexpr function Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: kariya_mitsuru at hotmail dot com I think that the sample code below should be compiled successfully. =========================================== #include <complex> static constexpr double d = std::real(10); int main() {} =========================================== Note that it is compiled successfully if the argument is std::complex<double>(10) instead of 10. According to C++11 standard 26.4.9[cmplx.over] paragraph 2, "if either argument has type complex<double>, double, or an integer type, then both arguments are effectively cast to complex<double>." Therefore, I think it should be compiled successfully too.
next reply other threads:[~2014-07-13 8:49 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-13 8:49 kariya_mitsuru at hotmail dot com [this message] 2014-07-13 9:00 ` [Bug libstdc++/61791] " kariya_mitsuru at hotmail dot com 2014-07-13 13:21 ` daniel.kruegler at googlemail dot com 2015-04-09 15:44 ` 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-61791-4@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).