public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/111272] [13/14 Regression] Truncated error messages with -std=c++23 and -std=c++26 Date: Fri, 01 Sep 2023 20:44:31 +0000 [thread overview] Message-ID: <bug-111272-4-mPdZ2XAq9C@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111272-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111272 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org Summary|Truncated error messages |[13/14 Regression] |with -std=c++23 and |Truncated error messages |-std=c++26 |with -std=c++23 and | |-std=c++26 Last reconfirmed| |2023-09-01 Target Milestone|--- |13.3 CC| |mpolacek at gcc dot gnu.org Status|UNCONFIRMED |ASSIGNED Keywords| |diagnostic --- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Started with r13-4112-gc85f8dbb173f45: commit c85f8dbb173f45053f6d8849d27adc98d9668769 Author: Marek Polacek <polacek@redhat.com> Date: Wed Nov 2 13:11:02 2022 -0400 c++: P2448 - Relaxing some constexpr restrictions [PR106649]
next prev parent reply other threads:[~2023-09-01 20:44 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-01 20:08 [Bug c++/111272] New: " pkeir at outlook dot com 2023-09-01 20:44 ` mpolacek at gcc dot gnu.org [this message] 2023-09-01 22:48 ` [Bug c++/111272] [13/14 Regression] " 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-mPdZ2XAq9C@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).