public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pkeir at outlook dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/111272] New: Truncated error messages with -std=c++23 and -std=c++26 Date: Fri, 01 Sep 2023 20:08:55 +0000 [thread overview] Message-ID: <bug-111272-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111272 Bug ID: 111272 Summary: Truncated error messages with -std=c++23 and -std=c++26 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: pkeir at outlook dot com Target Milestone: --- The C++14 code below requires the `constexpr` specifier on the `ft` member function. Compiling this with `-std=c++14`, `-std=c++17` or `-std=c++20` will provide a helpful error message which identifies the need to add the `constexpr` specifier to `ft`. However, if `-std=c++23`, or `-std=c++26` are used, no message indicating the need for `constexpr` on `ft` is displayed; and the message itself is truncated: ending only in "...not usable as a 'constexpr' function because:". struct Jam { // constexpr // n.b. int ft() { return 42; } constexpr Jam() { ft(); } }; constexpr bool test() { Jam j; return true; } static_assert(test(), ""); The full truncated error message is: $ /opt/gcc-latest/bin/g++ -std=c++26 -c truncated-constexpr-error-gcc.cpp truncated-constexpr-error-gcc.cpp:16:19: error: non-constant condition for static assertion 16 | static_assert(test(), ""); | ~~~~^~ truncated-constexpr-error-gcc.cpp:16:19: in ‘constexpr’ expansion of ‘test()’ truncated-constexpr-error-gcc.cpp:12:7: error: ‘constexpr Jam::Jam()’ called in a constant expression 12 | Jam j; | ^ truncated-constexpr-error-gcc.cpp:7:3: note: ‘constexpr Jam::Jam()’ is not usable as a ‘constexpr’ function because: 7 | Jam() { ft(); } | ^~~
next reply other threads:[~2023-09-01 20:08 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-01 20:08 pkeir at outlook dot com [this message] 2023-09-01 20:44 ` [Bug c++/111272] [13/14 Regression] " mpolacek at gcc dot gnu.org 2023-09-01 22:48 ` pkeir at outlook dot com 2023-09-04 10:50 ` de34 at live dot cn 2023-09-12 18:28 ` pkeir at outlook dot com 2023-09-14 14:16 ` mpolacek at gcc dot gnu.org 2023-10-16 12:33 ` cvs-commit at gcc dot gnu.org 2023-10-16 12:35 ` mpolacek at gcc dot gnu.org 2024-01-12 18:07 ` pkeir at outlook dot com 2024-01-12 19:14 ` mpolacek 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-111272-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).