public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/95958] [meta-bug] Inefficient arm_neon.h code for AArch64
Date: Mon, 29 Jun 2020 11:11:30 +0000 [thread overview]
Message-ID: <bug-95958-4-4lCqpApUgN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95958-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95958
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Depends on| |66675, 80283, 88212, 89057,
| |89606, 89967, 91753, 94442,
| |95265, 91598, 82074
--- Comment #1 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
At the time of writing, PR80283 doesn't have an AArch64 testcase,
only an AArch32 one. However, the underlying issue applies across
targets. The content probably overlaps a lot with PR91598, which
is AArch64-specific.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66675
[Bug 66675] Could improve vector lane folding style operations.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80283
[Bug 80283] [8/9/10/11 Regression] bad SIMD register allocation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82074
[Bug 82074] [aarch64] vmlsq_f32 compiled into 2 instructions
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88212
[Bug 88212] IRA Register Coalescing not working for the testcase
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89057
[Bug 89057] [8/9/10/11 Regression] AArch64 ld3 st4 less optimized
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89606
[Bug 89606] Extra mov after structure load instructions on aarch64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89967
[Bug 89967] Inefficient code generation for vld2q_lane_u8 under aarch64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91598
[Bug 91598] [8/9 regression] 60% speed drop on neon intrinsic loop
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91753
[Bug 91753] Bad register allocation of multi-register types
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94442
[Bug 94442] [10/11 regression] Redundant loads/stores emitted at -O3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95265
[Bug 95265] aarch64: suboptimal code generation for common neon intrinsic
sequence involving shrn and mull
next prev parent reply other threads:[~2020-06-29 11:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 11:03 [Bug target/95958] New: " rsandifo at gcc dot gnu.org
2020-06-29 11:04 ` [Bug target/95958] " rsandifo at gcc dot gnu.org
2020-06-29 11:11 ` rsandifo at gcc dot gnu.org [this message]
2021-02-10 12:36 ` ktkachov at gcc dot gnu.org
2021-02-10 12:43 ` ktkachov at gcc dot gnu.org
2021-05-17 8:55 ` rsandifo at gcc dot gnu.org
2021-08-12 8:09 ` tnfchris at gcc dot gnu.org
2021-08-17 10:13 ` mkuvyrkov at gcc dot gnu.org
2021-09-13 15:20 ` pinskia at gcc dot gnu.org
2023-08-04 17:22 ` pinskia at gcc dot gnu.org
2023-08-23 15:54 ` tnfchris at gcc dot gnu.org
2024-05-22 20:09 ` 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-95958-4-4lCqpApUgN@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).