public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/39094] loop_niter_by_eval should deal with &a[i_1]
Date: Mon, 03 Jan 2022 11:05:05 +0000 [thread overview]
Message-ID: <bug-39094-4-kVUjyX31da@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-39094-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39094
--- Comment #2 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 23 Dec 2021, pinskia at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39094
>
> Andrew Pinski <pinskia at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> See Also| |https://gcc.gnu.org/bugzill
> | |a/show_bug.cgi?id=66718
>
> --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> Hmm, do we need this any more after gimple-laddress (PR66718) was added?
Probably not, maybe only for "completeness" (there's cunrolli before
laddress I think)
prev parent reply other threads:[~2022-01-03 11:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-39094-4@http.gcc.gnu.org/bugzilla/>
2021-12-23 23:44 ` pinskia at gcc dot gnu.org
2022-01-03 11:05 ` rguenther at suse dot de [this message]
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=bug-39094-4-kVUjyX31da@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).