public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alalaw01 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/66791] New: Replace builtins with gcc vector extensions code
Date: Tue, 07 Jul 2015 16:12:00 -0000 [thread overview]
Message-ID: <bug-66791-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66791
Bug ID: 66791
Summary: Replace builtins with gcc vector extensions code
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: alalaw01 at gcc dot gnu.org
Blocks: 47562
Target Milestone: ---
Target: arm
Lots of ARM neon intrinsics are implemented using builtins backing onto
patterns in neon.md. These are opaque to the midend, but we could rewrite them
using equivalent gcc vector operations, that would be transparent to the midend
but would still eventually be turned into the same instructions. This would
enable more optimization in the midend.
Many of the AArch64 intrinsics have been implemented in this way so AArch64
arm_neon.h may provide some useful templates.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47562
[Bug 47562] [meta-bug] keep track of Neon Intrinsics enhancements
next reply other threads:[~2015-07-07 16:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 16:12 alalaw01 at gcc dot gnu.org [this message]
2015-07-29 8:41 ` [Bug target/66791] [ARM] " ramana at gcc dot gnu.org
2020-12-08 17:54 ` cvs-commit at gcc dot gnu.org
2020-12-16 6:06 ` cvs-commit at gcc dot gnu.org
2020-12-16 6:28 ` cvs-commit at gcc dot gnu.org
2020-12-16 7:47 ` cvs-commit at gcc dot gnu.org
2021-01-14 14:30 ` cvs-commit at gcc dot gnu.org
2021-05-04 12:32 ` rguenth at gcc dot gnu.org
2021-05-14 10:35 ` cvs-commit at gcc dot gnu.org
2021-06-21 9:25 ` prathamesh3492 at gcc dot gnu.org
2021-06-30 9:45 ` cvs-commit at gcc dot gnu.org
2021-07-12 9:50 ` cvs-commit at gcc dot gnu.org
2021-07-30 9:41 ` cvs-commit at gcc dot gnu.org
2021-08-11 10:02 ` cvs-commit 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-66791-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: 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).