public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/94034] [10 Regression] Broken diagnostic: 'result_decl' not supported by dump_expr
Date: Wed, 17 Feb 2021 15:01:57 +0000	[thread overview]
Message-ID: <bug-94034-4-xuYzWSaj9N@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94034-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94034

--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Patrick Palka
<ppalka@gcc.gnu.org>:

https://gcc.gnu.org/g:d7fa3fa5796a46deb308c8c38b247e290d97f1f6

commit r10-9372-gd7fa3fa5796a46deb308c8c38b247e290d97f1f6
Author: Patrick Palka <ppalka@redhat.com>
Date:   Wed Feb 17 09:55:42 2021 -0500

    c++: Revert EXPR_LOCATION change to build_aggr_init_expr [PR96997]

    My change in r10-7718 to make build_aggr_init_expr set EXPR_LOCATION
    (mimicking build_target_expr) causes the debuginfo regression PR96997.
    Given that this change is mostly independent of the rest of the commit,
    and that the only fallout of reverting it is a less accurate error
    message location in a testcase introduced in the same commit, it seems
    the best way forward is to just revert this part of the commit.

    gcc/cp/ChangeLog:

            PR debug/96997
            PR c++/94034
            * tree.c (build_aggr_init_expr): Revert r10-7718 change.

    gcc/testsuite/ChangeLog:

            PR debug/96997
            PR c++/94034
            * g++.dg/cpp1y/constexpr-nsdmi7b.C:  Adjust expected location of
            "call to non-'constexpr' function" error message.

    (cherry picked from commit 78a6d0e30d7950216dc0c5be5d65d0cbed13924c)

      parent reply	other threads:[~2021-02-17 15:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-94034-4@http.gcc.gnu.org/bugzilla/>
2020-03-20 11:43 ` rguenth at gcc dot gnu.org
2020-03-31 14:44 ` ppalka at gcc dot gnu.org
2020-04-01 14:36 ` paolo.carlini at oracle dot com
2020-04-02 15:29 ` ppalka at gcc dot gnu.org
2020-04-08 16:34 ` ppalka at gcc dot gnu.org
2020-04-09 18:31 ` jason at gcc dot gnu.org
2020-04-09 18:41 ` jason at gcc dot gnu.org
2020-04-14 15:23 ` cvs-commit at gcc dot gnu.org
2020-04-14 15:24 ` ppalka at gcc dot gnu.org
2021-02-17  1:49 ` cvs-commit at gcc dot gnu.org
2021-02-17 15:01 ` cvs-commit 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-94034-4-xuYzWSaj9N@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: link
Be 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).