From: Tom de Vries <tdevries@suse.de>
To: Alexandre Oliva <oliva@gnu.org>
Cc: Richard Biener <rguenther@suse.de>,
gcc-patches@gcc.gnu.org, Jakub Jelinek <jakub@redhat.com>,
Jim Wilson <wilson@tuliptree.org>
Subject: Re: [RFC 1/3, debug] Add fdebug-nops
Date: Tue, 24 Jul 2018 21:04:00 -0000 [thread overview]
Message-ID: <aba0ee75-0a43-5b73-ec86-ad052ec764b5@suse.de> (raw)
In-Reply-To: <ora7qg8ncu.fsf@lxoliva.fsfla.org>
On 07/24/2018 09:06 PM, Alexandre Oliva wrote:
> On Jul 24, 2018, Tom de Vries <tdevries@suse.de> wrote:
>
>> There's a design principle in GCC that code generation and debug generation
>> are independent. This guarantees that if you're encountering a problem in an
>> application without debug info, you can recompile it with -g and be certain
>> that you can reproduce the same problem, and use the debug info to debug the
>> problem. This invariant is enforced by bootstrap-debug. The fdebug-nops
>> breaks this invariant
>
> I thought of a way to not break it: enable the debug info generation
> machinery, including VTA and SFN, but discard those only at the very end
> if -g is not enabled. The downside is that it would likely slow -Og
> down significantly, but who uses it without -g anyway?
I thought of the same. I've submitted a patch here that uses SFN:
https://gcc.gnu.org/ml/gcc-patches/2018-07/msg01391.html . VTA is not
needed AFAIU.
Thanks,
- Tom
next prev parent reply other threads:[~2018-07-24 21:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 13:29 [RFC][debug] Add -fadd-debug-nops Tom de Vries
2018-07-16 13:34 ` Jakub Jelinek
2018-07-16 14:32 ` Tom de Vries
2018-07-17 1:02 ` Alexandre Oliva
2018-07-16 13:50 ` Richard Biener
2018-07-16 15:10 ` Tom de Vries
2018-07-24 11:30 ` Tom de Vries
2018-07-24 11:35 ` [RFC 1/3, debug] Add fdebug-nops Tom de Vries
2018-07-24 14:59 ` [PATCH, " Tom de Vries
2018-07-24 19:07 ` [RFC 1/3, " Alexandre Oliva
2018-07-24 21:04 ` Tom de Vries [this message]
2018-07-26 7:50 ` Alexandre Oliva
2018-07-24 11:37 ` [RFC 2/3, debug] Add fkeep-vars-live Tom de Vries
2018-07-24 11:46 ` Jakub Jelinek
2018-07-24 12:34 ` Tom de Vries
2018-07-24 15:03 ` [PATCH, " Tom de Vries
2018-07-25 11:06 ` Jakub Jelinek
2018-07-25 11:41 ` Richard Biener
2018-07-25 11:47 ` Richard Biener
2018-07-24 19:11 ` [RFC 2/3, " Alexandre Oliva
2018-07-25 11:02 ` Jakub Jelinek
2018-07-26 7:47 ` Alexandre Oliva
2018-07-24 11:38 ` [RFC 3/3, debug] Add fdebug-nops and fkeep-vars-live to Og only Tom de Vries
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=aba0ee75-0a43-5b73-ec86-ad052ec764b5@suse.de \
--to=tdevries@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=oliva@gnu.org \
--cc=rguenther@suse.de \
--cc=wilson@tuliptree.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).