public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth 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: Thu, 10 Sep 2020 09:29:43 +0000 [thread overview] Message-ID: <bug-96997-4-pOTwOTHQAA@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 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |needs-bisection --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- Now the question is whether/why we don't see any DW_TAG_inlined_subroutine and why we inline anything at -O0 at all. That said, the middle-end does not perform any inlining but the C++ FE inserts finally { [/usr/include/c++/10/bits/basic_string.h:525:59] std::allocator<char>::~allocator ([/usr/include/c++/10/bits/basic_string.h:525:59] &D.37009); } } finally { [/usr/include/c++/10/bits/basic_string.h:525:59] D.37009 = {CLOBBER}; } so somehow we leak the location of the dtor declaration to the GIMPLE stmt created by the gimplifier. Bisection is probably what is easiest to get us forward.
next prev parent reply other threads:[~2020-09-10 9:29 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 [this message] 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 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-pOTwOTHQAA@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).