public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vineetg at rivosinc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/106533] loop distribution not distributing inner loop (to memcpy) when perfect loop nest
Date: Tue, 16 Aug 2022 16:33:20 +0000 [thread overview]
Message-ID: <bug-106533-4-QLWihpJWJT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106533-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106533
--- Comment #9 from Vineet Gupta <vineetg at rivosinc dot com> ---
> > Can this be back-ported to gcc 12 please ?
>
> Do you have an indication that this is a regression?
No, but this does seem like a bug, aren't those backported ?
next prev parent reply other threads:[~2022-08-16 16:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 7:22 [Bug tree-optimization/106533] New: " vineetg at rivosinc dot com
2022-08-05 7:32 ` [Bug tree-optimization/106533] " vineetg at rivosinc dot com
2022-08-05 7:35 ` vineetg at rivosinc dot com
2022-08-05 7:41 ` vineetg at rivosinc dot com
2022-08-05 8:36 ` rguenth at gcc dot gnu.org
2022-08-05 10:12 ` cvs-commit at gcc dot gnu.org
2022-08-05 10:12 ` rguenth at gcc dot gnu.org
2022-08-16 4:40 ` vineetg at rivosinc dot com
2022-08-16 7:16 ` rguenth at gcc dot gnu.org
2022-08-16 16:33 ` vineetg at rivosinc dot com [this message]
2022-08-16 16:48 ` pinskia at gcc dot gnu.org
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-106533-4-QLWihpJWJT@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).