public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <rguenther@suse.de>
Cc: Jeff Law <law@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] strlen: Return TODO_update_address_taken when memcmp has been optimized [PR96271]
Date: Fri, 15 Jan 2021 21:31:10 +0100	[thread overview]
Message-ID: <20210115203110.GQ1034503@tucnak> (raw)
In-Reply-To: <0D5FC4D5-807C-41B8-9EDE-63983161A73A@suse.de>

On Fri, Jan 15, 2021 at 09:16:31PM +0100, Richard Biener wrote:
> >Apparently not.  The passes after strlen1 are:
> >pr96271.c.191t.thread4
> >pr96271.c.192t.vrp2
> >pr96271.c.193t.copyprop5
> >pr96271.c.194t.wrestrict
> >pr96271.c.195t.dse4
> >pr96271.c.196t.cddce3
> >pr96271.c.197t.forwprop4
> >pr96271.c.198t.phiopt4
> >pr96271.c.199t.fab1
> >pr96271.c.200t.widening_mul
> >pr96271.c.201t.store-merging
> >pr96271.c.202t.tailc
> >pr96271.c.203t.dce7
> >pr96271.c.204t.crited1
> >pr96271.c.206t.uncprop1
> >pr96271.c.207t.local-pure-const2
> >pr96271.c.208t.modref2
> >pr96271.c.242t.nrv
> >pr96271.c.243t.isel
> >pr96271.c.244t.optimized
> >and TODO_update_address_taken is used by the inliner, sra, ccp, loop
> >and
> >sccvn, so maybe in fre5 in 187.
> 
> OK, I think it makes sense to delay until before forwprop4 so can you instead arrange for an unconditional run there? 

At the end of forwprop4 or start (i.e. end of previous pass)?

	Jakub


  reply	other threads:[~2021-01-15 20:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15 18:32 Jakub Jelinek
2021-01-15 19:48 ` Richard Biener
2021-01-15 19:57   ` Jakub Jelinek
2021-01-15 20:16     ` Richard Biener
2021-01-15 20:31       ` Jakub Jelinek [this message]
2021-01-15 21:02         ` Jakub Jelinek
2021-01-16  1:00           ` Jakub Jelinek
2021-01-16  7:52             ` 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=20210115203110.GQ1034503@tucnak \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    --cc=rguenther@suse.de \
    /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).