public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Vladimir Makarov <vmakarov@redhat.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	Jeff Law <law@redhat.com>, "H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: [PATCH, LRA]: Revert the revert of removal of usless move insns.
Date: Sat, 20 Apr 2019 22:38:00 -0000	[thread overview]
Message-ID: <2907e871-7c16-2705-8aec-df5d4f41e6ba@redhat.com> (raw)
In-Reply-To: <CAFULd4aNv3xwZbW5AZGnDm17aqktn6xSWJQccS0iUPQUn28jwA@mail.gmail.com>


On 4/20/19 4:55 AM, Uros Bizjak wrote:
> On 4/20/19, Vladimir Makarov <vmakarov@redhat.com> wrote:
>> On 11/21/18 2:33 PM, Uros Bizjak wrote:
>>> Hello!
>>>
>>> Before the recent patch to post-reload mode switching, vzeroupper
>>> insertion depended on the existence of the return copy instructions
>>> pair in functions that return a value. The first instruction in the
>>> pair represents a move to a function return hard register, and the
>>> second was a USE of the function return hard register. Sometimes a nop
>>> move was generated (e.g. %eax->%eax) for the first instruction of the
>>> return copy instructions pair and the patch [1] teached LRA  to remove
>>> these useless instructions on the fly.
>>>
>>> The removal caused optimize mode switching to trigger the assert,
>>> since the first instruction of a return pair was not found. The
>>> relevant part of the patch was later reverted. With the recent
>>> optimize mode switching patch, this is no longer necessary for
>>> vzeroupper insertion pass, so attached patch reverts the revert.
>>>
>>> 2018-11-21  Uros Bizjak  <ubizjak@gmail.com>
>>>
>>>       Revert the revert:
>>>       2013-10-26  Vladimir Makarov  <vmakarov@redhat.com>
>>>
>>>       Revert:
>>>       2013-10-25  Vladimir Makarov  <vmakarov@redhat.com>
>>>
>>>       * lra-spills.c (lra_final_code_change): Remove useless move insns.
>>>
>>> Patch was bootstrapped and regression tested on x86_64-linux-gnu {,-m32}.
>>>
>>> OK for mainline?
>> Sure, Uros. I support the patch.  But I think it would be wise to
>> postpone its committing after releasing GCC-9.  Simply it is hard to
>> predict the patch effect to other targets and I would avoid any risk at
>> this stage.
> Actually, the "revert of the revert" patch was already committed to
> mainline some time ago.

Sorry for confusion, Uros. I did not check the date of your original 
posting.  Insn removal was added to RA just to avoid wasting CPU cycles 
on such insn processing afterwards.  Such insns are removed anyway later 
in the pass pipeline.  The CPU time savings are tiny but the removal 
creates too many problems including new one PR90178.  I should have 
avoided to put this code in the first place.

I think we should remove this code forever. It is not convenient for me 
to do this now because I am traveling.  If somebody wants to remove the 
code, i am approving this in advance.


> To clear the possible misunderstanding, let me summarise the issue:
>
> - the original patch that remove useless move insn caused a breakage
> in vzeroupper pass.
> - the original patch was reverted due to the above breakage
> - the vzeroupper pass was later adjusted to tolerate removed useless
> move instructions, and this cleared the way to revert the revert. Now
> LRA removes useless move insns.
>
> An orthogonal issue (PR90178) was discovered, showing that some passes
> also depend on the presence of useless move insn.
>
> The bisection stumbled on the "revert of the revert" patch that
> (obviously) re-introduced the issue. I'm not in the position to decide
> if useless move insn can be removed or if these later passes should be
> fixed, I can only say that the vzeroupper pass is now agnostic to the
> presence of useless move insns.
>
> Uros.

  reply	other threads:[~2019-04-20 21:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-21 19:33 Uros Bizjak
2018-11-21 21:45 ` Vladimir Makarov
2019-04-19 19:12   ` H.J. Lu
2019-04-20  6:14 ` Vladimir Makarov
2019-04-20 15:38   ` Uros Bizjak
2019-04-20 22:38     ` Vladimir Makarov [this message]
2019-04-21 20:27       ` [PATCH] LRA: Revert "Remove useless move insns" H.J. Lu

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=2907e871-7c16-2705-8aec-df5d4f41e6ba@redhat.com \
    --to=vmakarov@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=law@redhat.com \
    --cc=ubizjak@gmail.com \
    /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).