public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/64081] [10/11/12/13 Regression] r217828 prevents RTL loop unroll Date: Wed, 15 Mar 2023 23:54:40 +0000 [thread overview] Message-ID: <bug-64081-4-hCcYlU6ogI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64081-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64081 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |needs-bisection --- Comment #68 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Note for the original testcase in comment #0, GCC 9 starts to unroll the code again. There are gimple level changes that changed the IR again. Would be interesting to find out what patch changed that.
next prev parent reply other threads:[~2023-03-15 23:54 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-26 8:56 [Bug tree-optimization/64081] New: [5 Regression] r217827 " izamyatin at gmail dot com 2014-11-26 10:09 ` [Bug tree-optimization/64081] " rguenth at gcc dot gnu.org 2014-11-26 10:44 ` rguenth at gcc dot gnu.org 2014-11-26 10:44 ` rguenth at gcc dot gnu.org 2015-01-19 13:59 ` [Bug rtl-optimization/64081] " ienkovich at gcc dot gnu.org 2015-01-20 8:29 ` ienkovich at gcc dot gnu.org 2015-01-20 9:33 ` rguenth at gcc dot gnu.org 2015-01-20 22:01 ` law at redhat dot com 2015-01-20 22:02 ` pinskia at gcc dot gnu.org 2015-01-21 0:55 ` dje at gcc dot gnu.org 2015-01-21 20:01 ` izamyatin at gmail dot com 2015-01-21 20:02 ` izamyatin at gmail dot com 2015-01-22 2:33 ` dje at gcc dot gnu.org 2015-01-22 21:26 ` izamyatin at gmail dot com 2015-01-23 2:50 ` dje at gcc dot gnu.org 2015-01-26 18:51 ` izamyatin at gmail dot com 2015-02-20 10:53 ` jakub at gcc dot gnu.org 2015-02-20 11:53 ` izamyatin at gmail dot com 2015-03-24 18:21 ` steven at gcc dot gnu.org 2015-04-22 12:02 ` [Bug rtl-optimization/64081] [5/6 " jakub at gcc dot gnu.org 2015-07-16 9:17 ` rguenth at gcc dot gnu.org 2021-04-27 11:37 ` [Bug rtl-optimization/64081] [8/9/10/11/12 Regression] r217828 " jakub at gcc dot gnu.org 2021-07-28 7:04 ` [Bug rtl-optimization/64081] [9/10/11/12 " rguenth at gcc dot gnu.org 2022-04-21 7:47 ` rguenth at gcc dot gnu.org 2023-03-15 23:54 ` pinskia at gcc dot gnu.org [this message] 2023-05-29 10:01 ` [Bug rtl-optimization/64081] [10/11/12/13/14 " jakub at gcc dot gnu.org 2024-03-13 3:36 ` [Bug rtl-optimization/64081] [11/12 " law 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-64081-4-hCcYlU6ogI@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: linkBe 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).