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 debug/96997] [10/11 Regression] step over in gdb always stops in basic_string(const _CharT* __s, const _Alloc& __a = _Alloc())
Date: Wed, 17 Feb 2021 01:49:23 +0000 [thread overview]
Message-ID: <bug-96997-4-nsbeCvV71S@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96997-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96997
--- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>:
https://gcc.gnu.org/g:78a6d0e30d7950216dc0c5be5d65d0cbed13924c
commit r11-7263-g78a6d0e30d7950216dc0c5be5d65d0cbed13924c
Author: Patrick Palka <ppalka@redhat.com>
Date: Tue Feb 16 20:49:12 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.
next prev parent reply other threads:[~2021-02-17 1:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 12:29 [Bug debug/96997] New: " alexis.jeandet at member dot fsf.org
2020-09-09 15:47 ` [Bug debug/96997] " redi at gcc dot gnu.org
2020-09-10 7:29 ` [Bug debug/96997] [10/11 Regression] " rguenth at gcc dot gnu.org
2020-09-10 8:16 ` vries at gcc dot gnu.org
2020-09-10 8:19 ` vries at gcc dot gnu.org
2020-09-10 8:21 ` vries at gcc dot gnu.org
2020-09-10 9:29 ` rguenth at gcc dot gnu.org
2020-09-10 10:22 ` redi at gcc dot gnu.org
2021-02-16 17:01 ` jakub at gcc dot gnu.org
2021-02-16 17:10 ` jakub at gcc dot gnu.org
2021-02-16 17:29 ` jakub at gcc dot gnu.org
2021-02-16 18:11 ` ppalka at gcc dot gnu.org
2021-02-16 18:16 ` jakub at gcc dot gnu.org
2021-02-16 18:18 ` ppalka at gcc dot gnu.org
2021-02-17 1:49 ` cvs-commit at gcc dot gnu.org [this message]
2021-02-17 15:01 ` cvs-commit at gcc dot gnu.org
2021-02-23 3:12 ` ppalka at gcc dot gnu.org
2023-12-13 20:06 ` cvs-commit 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-96997-4-nsbeCvV71S@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).