From: Richard Biener <richard.guenther@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] opts: fix -gtoggle + optimize attribute
Date: Mon, 7 Mar 2022 14:48:45 +0100 [thread overview]
Message-ID: <CAFiYyc0R7W1JAHA5Eg9Lm0t-vCzDYV2JMd8S1jrpvVpnfctG4Q@mail.gmail.com> (raw)
In-Reply-To: <e3fe686b-a1f3-c4fe-1ec1-06f25339e007@suse.cz>
On Fri, Mar 4, 2022 at 2:12 PM Martin Liška <mliska@suse.cz> wrote:
>
> On 3/1/22 09:48, Richard Biener wrote:
> > I think moving flag_gtoggle handling before the flag_syntax_only handling
> > is a good thing. But I don't quite understand the flag_var_tracking disabling
> > or how it worked before.
>
> Well, as you know, the debugging options are a can of worms. During GCC 12 development I moved
> most of the option logic to finish_options which is a place that is used both for command line
> option processing and optimize/target pragma/attribute processing.
>
> That's why we see this problem. OPT_LEVELS_1_PLUS enables flag_var_tracking but we have to drop
> debug debug_info_level == DINFO_LEVEL_NONE.
>
> > At least I think you want to check for
> > debug_info_level == NONE, no? Why should DINFO_LEVEL_TERSE be
> > special?
>
> No, sending updated version of the patch.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Ready to be installed?
OK.
> Thanks,
> Martin
prev parent reply other threads:[~2022-03-07 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 9:03 Martin Liška
2022-03-01 8:48 ` Richard Biener
2022-03-04 13:12 ` Martin Liška
2022-03-07 13:48 ` Richard Biener [this message]
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=CAFiYyc0R7W1JAHA5Eg9Lm0t-vCzDYV2JMd8S1jrpvVpnfctG4Q@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
/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).