public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/97087] [11 regression] 70x slow -O3 Date: Fri, 18 Sep 2020 06:08:46 +0000 [thread overview] Message-ID: <bug-97087-4-lxSKEb0hew@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97087-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97087 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Target Milestone|--- |11.0 Keywords| |needs-bisection Last reconfirmed| |2020-09-18 Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed, mine. Curious which change triggered it. tree slp vectorization : 7.13 ( 98%) 0.01 (100%) 7.15 ( 98%) 228 kB ( 8%)
next prev parent reply other threads:[~2020-09-18 6:08 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-17 14:49 [Bug c/97087] New: " dimhen at gmail dot com 2020-09-17 14:55 ` [Bug c/97087] " dimhen at gmail dot com 2020-09-18 6:08 ` rguenth at gcc dot gnu.org [this message] 2020-09-18 6:36 ` [Bug middle-end/97087] " rguenth 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-97087-4-lxSKEb0hew@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).