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/107154] [12/13 Regression] GDB jumping to end of block when stepping over construction of local variable
Date: Tue, 04 Oct 2022 22:54:13 +0000 [thread overview]
Message-ID: <bug-107154-4-V9EvQn2hUx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107154-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107154
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>:
https://gcc.gnu.org/g:ce3a1b5976079b1467473b4628f05797fd2eae08
commit r13-3072-gce3a1b5976079b1467473b4628f05797fd2eae08
Author: Jason Merrill <jason@redhat.com>
Date: Tue Oct 4 17:06:04 2022 -0400
c++: fix debug info for array temporary [PR107154]
In the testcase the elaboration of the array init that happens at
genericize
time was getting the location info for the end of the function; fixed by
doing the expansion at the location of the original expression.
PR c++/107154
gcc/cp/ChangeLog:
* cp-gimplify.cc (cp_genericize_init_expr): Use iloc_sentinel.
(cp_genericize_target_expr): Likewise.
gcc/testsuite/ChangeLog:
* g++.dg/debug/dwarf2/lineno-array1.C: New test.
next prev parent reply other threads:[~2022-10-04 22:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 20:43 [Bug debug/107154] New: " redi at gcc dot gnu.org
2022-10-04 20:44 ` [Bug debug/107154] " redi at gcc dot gnu.org
2022-10-04 20:44 ` pinskia at gcc dot gnu.org
2022-10-04 20:48 ` [Bug debug/107154] [12/13 Regression] " jason at gcc dot gnu.org
2022-10-04 21:01 ` redi at gcc dot gnu.org
2022-10-04 22:54 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-06 10:39 ` [Bug debug/107154] [12 " rguenth at gcc dot gnu.org
2023-04-18 20:45 ` cvs-commit at gcc dot gnu.org
2023-04-18 20:47 ` jason 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-107154-4-V9EvQn2hUx@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).