From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <rguenther@suse.de>
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:21:25 +0200 [thread overview]
Message-ID: <YkG2VXHxsArgEDUo@tucnak> (raw)
In-Reply-To: <20220328131625.05BFC13215@imap2.suse-dmz.suse.de>
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?
> 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
next prev parent reply other threads:[~2022-03-28 13:22 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 [this message]
2022-03-28 13:26 ` Richard Biener
2022-03-28 13:29 ` Richard Biener
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=YkG2VXHxsArgEDUo@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=msebor@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).