public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Eric Botcazou <botcazou@adacore.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Restore RTL alias analysis for hard frame pointer
Date: Fri, 28 Oct 2022 14:27:15 +0200	[thread overview]
Message-ID: <CAFiYyc2xwnpfgzR4zggpjsffecEEMhGA3A3O4pfW+D1eEXJRUw@mail.gmail.com> (raw)
In-Reply-To: <1930502.usQuhbGJ8B@fomalhaut>

On Fri, Oct 28, 2022 at 11:11 AM Eric Botcazou via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> Hi,
>
> the following change:
>
> 2021-07-28  Bin Cheng  <bin.cheng@linux.alibaba.com>
>
>         * alias.c (init_alias_analysis): Don't skip prologue/epilogue.
>
> broke the alias analysis for the hard frame pointer (when it is used as a
> frame pointer, i.e. when the frame pointer is not eliminated) described in the
> large comment at the top of the file, because static_reg_base_value is set for
> it and, consequently, new_reg_base_value too.  So when the instruction saving
> the stack pointer into the hard frame pointer in the prologue is processed, it
> is viewed as a second set of the hard frame pointer and to a different value
> by record_set, which then resets new_reg_base_value to 0 and the game is over.
>
> This e.g. hampers the performance of the var-tracking RTL pass for parameters
> passed on the stack like on x86, leading to regressions when debugging, but
> code generation is very likely affected too.
>
> Bootstrapped/regtested on x86-64/Linux, OK for mainline and 12 branch?

OK for trunk and 12 after a while of burn-in.

Thanks,
Richard.

>
> 2022-10-28  Eric Botcazou  <ebotcazou@adacore.com>
>
>         * alias.cc (init_alias_analysis): Do not record sets to the hard
>         frame pointer if the frame pointer has not been eliminated.
>
> --
> Eric Botcazou

  reply	other threads:[~2022-10-28 12:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-28  9:10 Eric Botcazou
2022-10-28 12:27 ` Richard Biener [this message]
2022-10-28 12:27   ` Richard Biener
2022-10-29  8:19     ` Eric Botcazou
2022-10-29 11:03       ` Richard Biener
2022-11-09  9:47     ` Eric Botcazou
2022-11-09 10:44       ` 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=CAFiYyc2xwnpfgzR4zggpjsffecEEMhGA3A3O4pfW+D1eEXJRUw@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).