public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Claudiu Zissulescu Ianculescu <claziss@gmail.com>
To: gcc@gcc.gnu.org
Subject: Fwd: Possible regression in DF analysis
Date: Tue, 20 Dec 2022 14:34:33 +0200	[thread overview]
Message-ID: <CAL0iMy1doMftby_sffhjK=fwKneRgiHBQvTx4z+HcC1YUcWR2w@mail.gmail.com> (raw)
In-Reply-To: <CAL0iMy1ad0PmprQdu6BMhHdivPz--1Yq72+n02Lj-SmxhZmxQQ@mail.gmail.com>

+ gcc mailing list

---------- Forwarded message ---------
From: Claudiu Zissulescu Ianculescu <claziss@gmail.com>
Date: Tue, Dec 20, 2022 at 2:31 PM
Subject: Re: Possible regression in DF analysis
To: Jeff Law <jeffreyalaw@gmail.com>


Hi Jeff,

> Or is that the core of the problem -- that life analysis is inaccurate
> or unavailable?
>
The life analysis is not accurate/missing and loop-doloop check is not
performed, leading in inserting the doloop end pattern when it
shouldn't.
The issue is how df_analyse_loop sets the df problem subset, not
including the destination BB from the exit edges of a loop. I am
looking now how loop_post_order_compute and
loop_inverted_post_order_compute can include those missing BBs too.

Thanks,
Claudiu

      parent reply	other threads:[~2022-12-20 12:34 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
2022-12-17  0:33     ` Jeff Law
     [not found]       ` <CAL0iMy1ad0PmprQdu6BMhHdivPz--1Yq72+n02Lj-SmxhZmxQQ@mail.gmail.com>
2022-12-20 12:34         ` Claudiu Zissulescu Ianculescu [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='CAL0iMy1doMftby_sffhjK=fwKneRgiHBQvTx4z+HcC1YUcWR2w@mail.gmail.com' \
    --to=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).