From: Richard Biener <rguenther@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org, msebor@redhat.com
Subject: Re: [PATCH] tree-optimization/105080 - make sure SCEV is available for ranger
Date: Mon, 28 Mar 2022 15:29:23 +0200 (CEST) [thread overview]
Message-ID: <56r269p8-98p7-n2p4-o4o3-q12qpo670s7@fhfr.qr> (raw)
In-Reply-To: <2orq11q-7817-95q3-2p9r-s3q5958q1r@fhfr.qr>
On Mon, 28 Mar 2022, Richard Biener wrote:
> On Mon, 28 Mar 2022, Jakub Jelinek wrote:
>
> > On Mon, Mar 28, 2022 at 03:16:24PM +0200, Richard Biener wrote:
> > > When doing format diagnostics at -O0 we should make sure to make
> > > SCEV available to avoid false positives due to ranges we otherwise
> > > can trivially compute.
> > >
> > > Bootstrap and regtest running on x86_64-unknown-linux-gnu.
> > >
> > > OK if that succeeds?
> >
> > Doesn't this slow down -O0 compilation too much?
>
> Not if you do not enable the warning. If you enable it you
> probably are set to pay for it. Are you specifically
> concerned about the cases where SCEV / niter analysis take
> a lot of time or are you concerned about the constant overhead
> of enabling loops/SCEV?
One concern might be that loop_optimizer_init (LOOPS_NORMAL)
changes the IL but the early pass just emits diagnostics so
when disabled/enabled (based purely on diagnostic options)
generated code could change. Note SCEV currently has (undocumented)
contraints on loops so just AVOID_CFG_MANIPULATIONS doens't work
there without putting it extra safety checks to give up.
Richard.
> Richard.
>
> > > 2022-03-28 Richard Biener <rguenther@suse.de>
> > >
> > > PR tree-optimization/105080
> > > * tree-ssa-strlen.cc (printf_strlen_execute): Always init
> > > loops and SCEV.
> > >
> > > * gcc.dg/pr105080.c: New testcase.
> >
> > Jakub
> >
> >
>
>
--
Richard Biener <rguenther@suse.de>
SUSE Software Solutions Germany GmbH, Maxfeldstrasse 5, 90409 Nuernberg,
Germany; GF: Ivo Totev; HRB 36809 (AG Nuernberg)
next prev parent reply other threads:[~2022-03-28 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 13:16 Richard Biener
2022-03-28 13:21 ` Jakub Jelinek
2022-03-28 13:26 ` Richard Biener
2022-03-28 13:29 ` Richard Biener [this message]
2022-03-28 13:38 ` Jakub Jelinek
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=56r269p8-98p7-n2p4-o4o3-q12qpo670s7@fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=msebor@redhat.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).