From: Jeff Law <jeffreyalaw@gmail.com>
To: Richard Biener <rguenther@suse.de>, gcc-patches@gcc.gnu.org
Cc: Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] lto/109263 - lto-wrapper and -g0 -ggdb
Date: Sun, 2 Apr 2023 15:16:48 -0600 [thread overview]
Message-ID: <92d404e9-d5c6-45d8-58c3-cb07c51287a5@gmail.com> (raw)
In-Reply-To: <20230323160030.02D4813596@imap2.suse-dmz.suse.de>
On 3/23/23 10:00, Richard Biener via Gcc-patches wrote:
> The following makes lto-wrapper deal with non-combined debug
> disabling / enabling option combinations properly. Interestingly
> -gno-dwarf also enables debug.
>
> Bootstrap / regtest running on x86_64-unknown-linux-gnu.
>
> OK? Or do we want to try harder to zap earlier -g0 when later
> -g* appear?
>
> PR lto/109263
> * lto-wrapper.c (run_gcc): Parse alternate debug options
> as well, they always enable debug.
So I think the agreement was that later -g options override, but don't
completely disable. So OK.
Jeff
next prev parent reply other threads:[~2023-04-02 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 16:00 Richard Biener
2023-04-02 21:16 ` Jeff Law [this message]
2023-03-27 6:46 Richard Biener
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=92d404e9-d5c6-45d8-58c3-cb07c51287a5@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--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).