public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/101598] [debug, ada] .loc generated for defs__struct1IP Date: Fri, 23 Jul 2021 12:42:47 +0000 [thread overview] Message-ID: <bug-101598-4-IKd1LpH5LA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101598-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101598 --- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> --- FWIW, this works for me: ... $ git diff diff --git a/gcc/dwarf2out.c b/gcc/dwarf2out.c index 82783c4968b..0e21775041c 100644 --- a/gcc/dwarf2out.c +++ b/gcc/dwarf2out.c @@ -28390,6 +28390,8 @@ dwarf2out_source_line (unsigned int line, unsigned int column, column = 0; file_num = maybe_emit_file (lookup_filename (filename)); + if (DECL_IGNORED_P (cfun->decl) && is_ada ()) + return; /* ??? TODO: Elide duplicate line number entries. Traditionally, the debugger has used the second (possibly duplicate) line number ...
next prev parent reply other threads:[~2021-07-23 12:42 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-23 12:35 [Bug debug/101598] New: " vries at gcc dot gnu.org 2021-07-23 12:42 ` vries at gcc dot gnu.org [this message] 2021-07-23 12:54 ` [Bug debug/101598] " bernd.edlinger at hotmail dot de 2021-07-23 12:55 ` vries at gcc dot gnu.org 2021-07-23 13:05 ` vries at gcc dot gnu.org 2021-07-23 13:08 ` bernd.edlinger at hotmail dot de 2021-07-24 6:11 ` bernd.edlinger at hotmail dot de 2021-07-24 19:26 ` bernd.edlinger at hotmail dot de 2021-08-04 14:26 ` bernd.edlinger at hotmail dot de 2021-08-11 5:30 ` cvs-commit at gcc dot gnu.org 2021-08-11 7:20 ` edlinger at gcc dot gnu.org 2022-10-25 10:24 ` cvs-commit at gcc dot gnu.org 2022-10-25 10:25 ` 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-101598-4-IKd1LpH5LA@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).