From: Richard Biener <richard.guenther@gmail.com>
To: Eric Botcazou <botcazou@adacore.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Avoid creating useless debug temporaries
Date: Wed, 26 Apr 2023 11:48:50 +0200 [thread overview]
Message-ID: <CAFiYyc33xZQ1=V0fw_CYHc89av-djvib50bnUvZLiZ5iK7V9=w@mail.gmail.com> (raw)
In-Reply-To: <4477930.LvFx2qVVIh@fomalhaut>
On Wed, Apr 26, 2023 at 11:31 AM Eric Botcazou <botcazou@adacore.com> wrote:
>
> > probably also helps PR109612 and the other similar PR referenced therein.
>
> Here's a more aggressive patch in this area, but it regresses guality tests,
> for example:
>
> +FAIL: gcc.dg/guality/ipa-sra-1.c -O2 -DPREVENT_OPTIMIZATION line 27 k ==
> 3
> +FAIL: gcc.dg/guality/ipa-sra-1.c -O3 -g -DPREVENT_OPTIMIZATION line 27 k
> == 3
> +FAIL: gcc.dg/guality/ipa-sra-1.c -Os -DPREVENT_OPTIMIZATION line 27 k ==
> 3
>
> eric@fomalhaut:~/build/gcc/native> diff -u ipa-sra-1.c.254t.optimized.0 ipa-
> sra-1.c.254t.optimized
> --- ipa-sra-1.c.254t.optimized.0 2023-04-26 11:12:07.806357325 +0200
> +++ ipa-sra-1.c.254t.optimized 2023-04-26 11:24:08.632874257 +0200
> @@ -101,7 +101,6 @@
> # DEBUG k => k_5
> # DEBUG BEGIN_STMT
> _1 = get_val1 ();
> - # DEBUG D#6 => k_5
> r_8 = foo.isra (_1);
> # DEBUG r => r_8
> # DEBUG BEGIN_STMT
>
> and I don't understand why yet.
interesting. So that removes unmentioned debug temporaries? I think
remove_unused_locals does something to debug stmts as well
(but from a quick look cannot decipher what it actually does).
On the RTL level delete_trivially_dead_insns does wipe some (redundant)
debug_insns, there's no exact match to that on the GIMPLE side either.
I'm not sure if DCE is a good place to do this.
>
> * tree-ssa-dce.cc (find_debug_expr_decl): New callback.
> (mark_stmt_if_obviously_necessary): Add DECLS parameters.
> <GIMPLE_DEBUG>: Call find_debug_expr_decl on the value of
> DEBUG_BIND statements and record the results in DECLS.
> (find_obviously_necessary_stmts): If DEBUG_BIND statements may be
> present, get rid of those setting an unnecessary DEBUG_EXPR_DECL.
>
> --
> Eric Botcazou
prev parent reply other threads:[~2023-04-26 9:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 9:33 Eric Botcazou
2023-04-25 15:10 ` Richard Biener
2023-04-25 15:20 ` Jakub Jelinek
2023-04-25 15:35 ` Eric Botcazou
2023-04-25 15:37 ` Jakub Jelinek
2023-04-26 9:31 ` Eric Botcazou
2023-04-26 9: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='CAFiYyc33xZQ1=V0fw_CYHc89av-djvib50bnUvZLiZ5iK7V9=w@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=botcazou@adacore.com \
--cc=gcc-patches@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).