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++/70819] constexpr error location wrong Date: Mon, 04 Dec 2023 19:23:19 +0000 [thread overview] Message-ID: <bug-70819-4-yLTzR4OKEb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-70819-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70819 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |mpolacek at gcc dot gnu.org Keywords|needs-bisection | Resolution|--- |FIXED --- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Changed in r14-2771 commit 5ebe5bcf8b6b6a0de16737b717e8bd06e4950a14 Author: Nathaniel Shead <nathanieloshead@gmail.com> Date: Sun Jul 23 01:13:43 2023 +1000 c++: Improve location information in constant evaluation So I guess fixed.
prev parent reply other threads:[~2023-12-04 19:23 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-70819-4@http.gcc.gnu.org/bugzilla/> 2023-12-02 3:33 ` pinskia at gcc dot gnu.org 2023-12-04 19:23 ` mpolacek at gcc dot gnu.org [this message]
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-70819-4-yLTzR4OKEb@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).