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/105940] suggested_unroll_factor applying place looks wrong
Date: Thu, 23 Jun 2022 06:28:31 +0000 [thread overview]
Message-ID: <bug-105940-4-8VHFiDJlUt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105940-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105940
--- Comment #13 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 23 Jun 2022, linkw at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105940
>
> Kewen Lin <linkw at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Resolution|--- |FIXED
> Status|ASSIGNED |RESOLVED
>
> --- Comment #12 from Kewen Lin <linkw at gcc dot gnu.org> ---
> Both backports were bootstrapped on ppc64le and aarch64, the extra aarch64 case
> was also verified.
>
> Guess we don't want to backport r13-1173 as the fixed inconsistent slp decision
> will not cause functionality correctness issue? Marking this as resolved.
Yeah, that one doesn't look for backporting.
prev parent reply other threads:[~2022-06-23 6:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 5:59 [Bug tree-optimization/105940] New: " linkw at gcc dot gnu.org
2022-06-13 6:07 ` [Bug tree-optimization/105940] " linkw at gcc dot gnu.org
2022-06-13 6:08 ` linkw at gcc dot gnu.org
2022-06-13 8:25 ` rguenth at gcc dot gnu.org
2022-06-14 5:58 ` cvs-commit at gcc dot gnu.org
2022-06-14 8:46 ` linkw at gcc dot gnu.org
2022-06-15 10:13 ` cvs-commit at gcc dot gnu.org
2022-06-16 13:33 ` linkw at gcc dot gnu.org
2022-06-16 13:35 ` linkw at gcc dot gnu.org
2022-06-17 10:56 ` linkw at gcc dot gnu.org
2022-06-20 12:45 ` cvs-commit at gcc dot gnu.org
2022-06-23 1:59 ` cvs-commit at gcc dot gnu.org
2022-06-23 2:25 ` cvs-commit at gcc dot gnu.org
2022-06-23 3:20 ` linkw at gcc dot gnu.org
2022-06-23 6:28 ` 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-105940-4-8VHFiDJlUt@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).