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 ada/101575] [gcc-11, -gdwarf-4] Missing .file <n> directive causes invalid line info
Date: Fri, 23 Jul 2021 12:36:32 +0000 [thread overview]
Message-ID: <bug-101575-4-amrJmsNxzy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101575-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101575
--- Comment #9 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Eric Botcazou from comment #7)
> (> More specifically, it's gone because we have:
> > ...
> > $ more defs.s
> > .file "defs.adb"
> > .text
> > .Ltext0:
> > .align 2
> > .globl defs__struct1IP
> > .type defs__struct1IP, @function
> > defs__struct1IP:
> > .LFB2:
> > .cfi_startproc
> > .file 1 "defs.ads"
> > .loc 1 18 9
> > ...
>
> Ugh, we do *not* want to have .loc directives for defs__struct1IP so
> something is even more broken here.
Filed as PR101598 - [debug, ada] .loc generated for defs__struct1IP.
next prev parent reply other threads:[~2021-07-23 12:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 9:37 [Bug debug/101575] New: " vries at gcc dot gnu.org
2021-07-22 12:30 ` [Bug debug/101575] " ebotcazou at gcc dot gnu.org
2021-07-22 12:32 ` vries at gcc dot gnu.org
2021-07-22 12:54 ` [Bug ada/101575] " ebotcazou at gcc dot gnu.org
2021-07-22 13:32 ` bernd.edlinger at hotmail dot de
2021-07-22 15:57 ` vries at gcc dot gnu.org
2021-07-22 16:00 ` vries at gcc dot gnu.org
2021-07-22 16:53 ` ebotcazou at gcc dot gnu.org
2021-07-23 12:22 ` bernd.edlinger at hotmail dot de
2021-07-23 12:36 ` vries at gcc dot gnu.org [this message]
2021-07-23 15:14 ` ebotcazou at gcc dot gnu.org
2021-07-24 7:43 ` bernd.edlinger at hotmail dot de
2021-07-24 11:21 ` bernd.edlinger at hotmail dot de
2021-07-24 12:24 ` ebotcazou at gcc dot gnu.org
2021-08-04 14:19 ` 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-101575-4-amrJmsNxzy@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).