public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91598] [8/9 regression] 60% speed drop on neon intrinsic loop
Date: Mon, 11 Jan 2021 20:35:07 +0000 [thread overview]
Message-ID: <bug-91598-4-8XUXWZosJO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91598-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91598
Wilco <wilco at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wilco at gcc dot gnu.org
--- Comment #7 from Wilco <wilco at gcc dot gnu.org> ---
Fixed in GCC9 and trunk. Given the regression is so large, it is worth
backporting.
The other issue is that assembler statements (and likely any RTL instruction
without specified latencies) are badly scheduled. Honoring all known latencies
and assuming a reasonable default latency otherwise would be a better approach.
next prev parent reply other threads:[~2021-01-11 20:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-91598-4@http.gcc.gnu.org/bugzilla/>
2020-03-11 12:08 ` marxin at gcc dot gnu.org
2021-01-11 20:35 ` wilco at gcc dot gnu.org [this message]
2021-05-05 12:25 ` clyon at gcc dot gnu.org
2021-05-14 9:52 ` [Bug target/91598] [9 " jakub at gcc dot gnu.org
2021-06-01 8:15 ` rguenth at gcc dot gnu.org
2021-08-12 7:29 ` tnfchris at gcc dot gnu.org
2021-08-12 7:40 ` mkuvyrkov at gcc dot gnu.org
2021-08-12 7:46 ` tnfchris at gcc dot gnu.org
2021-08-17 10:12 ` cvs-commit at gcc dot gnu.org
2021-08-17 10:13 ` mkuvyrkov 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-91598-4-8XUXWZosJO@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).