public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eric Botcazou <botcazou@adacore.com>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>
Cc: gcc-patches@gcc.gnu.org, Richard Biener <rguenther@suse.de>,
	Arnaud Charlet <charlet@adacore.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 2/2] Ada: Remove debug line number for DECL_IGNORED_P functions
Date: Wed, 04 Aug 2021 16:33:02 +0200	[thread overview]
Message-ID: <2152447.iZASKD2KPV@arcturus> (raw)
In-Reply-To: <AM8PR10MB47082DDF5950A51987290174E4EF9@AM8PR10MB4708.EURPRD10.PROD.OUTLOOK.COM>

> The location of these ignored Ada decls looks completely sane to me.
> However, it was an unintentional side effect of the patch to allow
> minimal debugging of ignored decls.  This means we can now step into
> those functions or set line breakpoints there, while previously that
> was not possible.  And I guess it could be considered an improvement.
> 
> So it's your choice, how you want these functions to be debugged.

The requirement on the GDB side is that these functions *cannot* be stepped 
into, i.e. that they be completely transparent for the GDB user.  But we still 
want to have location information in the compiler itself to debug it.

-- 
Eric Botcazou



  reply	other threads:[~2021-08-04 14:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-26 16:45 Bernd Edlinger
2021-08-02 13:07 ` Eric Botcazou
2021-08-02 17:18   ` Bernd Edlinger
2021-08-04 14:33     ` Eric Botcazou [this message]
2021-08-04 17:59       ` Bernd Edlinger
2021-08-09 14:37         ` Eric Botcazou
2021-08-10  7:23           ` Richard Biener
2021-08-10 15:46             ` Eric Botcazou
2021-08-10  9:43           ` Bernd Edlinger
2021-08-10 20:56             ` Eric Botcazou
2021-08-11  5:27               ` Bernd Edlinger

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=2152447.iZASKD2KPV@arcturus \
    --to=botcazou@adacore.com \
    --cc=bernd.edlinger@hotmail.de \
    --cc=charlet@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rguenther@suse.de \
    /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).