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] New: [meta-bug] Inefficient arm_neon.h code for AArch64 Date: Mon, 29 Jun 2020 11:03:55 +0000 [thread overview] Message-ID: <bug-95958-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95958 Bug ID: 95958 Summary: [meta-bug] Inefficient arm_neon.h code for AArch64 Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: meta-bug Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: rsandifo at gcc dot gnu.org Target Milestone: --- Target: aarch64*-*-* This meta-bug is to collect AArch64 performance improvements that require or have a strong relationship with arm_neon.h intrinsics. This PR overlaps to some extent with PR47562, but that PR is more general in two respects: it covers general arm_neon.h improvements, and it covers both AArch32 and AArch64.
next reply other threads:[~2020-06-29 11:03 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-29 11:03 rsandifo at gcc dot gnu.org [this message] 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 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@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).