From: Richard Biener <richard.guenther@gmail.com>
To: Claudiu Zissulescu Ianculescu <claziss@gmail.com>
Cc: Eric Botcazou <botcazou@adacore.com>, gcc@gcc.gnu.org
Subject: Re: Possible regression in DF analysis
Date: Wed, 14 Dec 2022 13:39:35 +0100 [thread overview]
Message-ID: <CAFiYyc1cXc1p7X+SK+YaXu8To6HUQqu=_U88bPYS9wP9VyrWVg@mail.gmail.com> (raw)
In-Reply-To: <CAL0iMy0z078wE-5Oi+GEkmQe+=FV76RHW33tuH_YTYspKyr3=g@mail.gmail.com>
On Wed, Dec 14, 2022 at 12:30 PM Claudiu Zissulescu Ianculescu
<claziss@gmail.com> wrote:
>
> Hi Richard,
>
> Sorry for my misunderstanding. I am calling the df_analyze() instead
> of df_analyze1() at the end. Shouldn't df_analyze take care and
> compute the correct postorder (df-core.cc:1273) ?
The point of df_analyze_loop is to be more efficient than doing a
full df_analyze (but of course that's only so in a limited way, still ...)
> Thank you,
> Claudiu
>
> On Wed, Dec 14, 2022 at 1:06 PM Richard Biener
> <richard.guenther@gmail.com> wrote:
> >
> > On Wed, Dec 14, 2022 at 11:37 AM Claudiu Zissulescu Ianculescu
> > <claziss@gmail.com> wrote:
> > >
> > > I have update the fix to this one:
> > >
> > > diff --git a/gcc/df-core.cc b/gcc/df-core.cc
> > > index a901b84878f..cc6383990a1 100644
> > > --- a/gcc/df-core.cc
> > > +++ b/gcc/df-core.cc
> > > @@ -1437,7 +1437,16 @@ df_analyze_loop (class loop *loop)
> > > df_set_blocks (blocks);
> > > BITMAP_FREE (blocks);
> > >
> > > - df_analyze_1 ();
> > > + /* Iterate over loop's exit edges and add theirs destinations BB
> > > + indexes. */
> > > + struct loop_exit *exit;
> > > + for (exit = loop->exits->next; exit->e; exit = exit->next)
> > > + bitmap_set_bit (df->blocks_to_analyze, exit->e->dest->index);
> >
> > I think you want to adjust the local 'blocks' bitmap passed to df_set_blocks.
> > There's also the issue that the computed postorder doesn't include the new
> > blocks and thus the computation will likely be invalid?
> >
> > > +
> > > + if (dump_file)
> > > + debug_bitmap_file (dump_file, df->blocks_to_analyze);
> > > +
> > > + df_analyze ();
> > > }
> > >
> > > I still need to validate it for x86
> > >
> > > Best,
> > > Claudiu
> > >
> > > On Tue, Dec 13, 2022 at 7:38 PM Claudiu Zissulescu Ianculescu
> > > <claziss@gmail.com> wrote:
> > > >
> > > > >
> > > > > Maybe you want to iterate over the loops exit edges and include their destination block instead?
> > > > >
> > > >
> > > > This is better approach, let me try it and I will be back to you.
> > > >
> > > > Thanks,
> > > > Claudiu
next prev parent reply other threads:[~2022-12-14 12:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 10:40 Claudiu Zissulescu Ianculescu
2022-12-08 11:33 ` Eric Botcazou
2022-12-08 11:51 ` Claudiu Zissulescu Ianculescu
2022-12-13 8:41 ` Eric Botcazou
2022-12-13 12:30 ` Claudiu Zissulescu Ianculescu
2022-12-13 16:53 ` Claudiu Zissulescu Ianculescu
2022-12-13 17:01 ` Richard Biener
2022-12-13 17:38 ` Claudiu Zissulescu Ianculescu
2022-12-14 10:37 ` Claudiu Zissulescu Ianculescu
2022-12-14 11:06 ` Richard Biener
2022-12-14 11:30 ` Claudiu Zissulescu Ianculescu
2022-12-14 12:39 ` Richard Biener [this message]
2022-12-17 0:33 ` Jeff Law
[not found] ` <CAL0iMy1ad0PmprQdu6BMhHdivPz--1Yq72+n02Lj-SmxhZmxQQ@mail.gmail.com>
2022-12-20 12:34 ` Fwd: " Claudiu Zissulescu Ianculescu
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='CAFiYyc1cXc1p7X+SK+YaXu8To6HUQqu=_U88bPYS9wP9VyrWVg@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=botcazou@adacore.com \
--cc=claziss@gmail.com \
--cc=gcc@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).