From: "James Greenhalgh" <james.greenhalgh@arm.com>
To: "James Greenhalgh" <James.Greenhalgh@arm.com>, <gcc-patches@gcc.gnu.org>
Cc: "Marcus Shawcroft" <Marcus.Shawcroft@arm.com>
Subject: *ping* [PATCH] [AArch64] Refactor Advanced SIMD builtin initialisation.
Date: Mon, 19 Nov 2012 09:51:00 -0000 [thread overview]
Message-ID: <000601cdc63b$5cb49100$161db300$@greenhalgh@arm.com> (raw)
In-Reply-To: <1352721593-9314-1-git-send-email-james.greenhalgh@arm.com>
> -----Original Message-----
> From: gcc-patches-owner@gcc.gnu.org [mailto:gcc-patches-
> owner@gcc.gnu.org] On Behalf Of James Greenhalgh
> Sent: 12 November 2012 12:00
> To: gcc-patches@gcc.gnu.org
> Cc: Marcus Shawcroft
> Subject: Re: [PATCH] [AArch64] Refactor Advanced SIMD builtin
> initialisation.
>
>
> Hi,
>
> This patch is a cleanup of the initialisation code for the
> SIMD builtins in the AArch64 port.
>
> We do this in preparation for later patches supporting
> TARGET_BUILTIN_DECL and
> TARGET_VECTORIZE_BUILTIN_VECTORIZABLE_FUNCTION.
>
> This patch supersedes another, similar patch I posted a few weeks
> ago (http://gcc.gnu.org/ml/gcc-patches/2012-10/msg00532.html) which
> was OKed, but not committed.
>
> The patch has been regression tested on aarch64-none-elf.
>
> Is this new version OK to commit?
Ping?
> Thanks,
> James Greenhalgh
>
next prev parent reply other threads:[~2012-11-19 9:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 15:53 James Greenhalgh
2012-10-15 11:35 ` Marcus Shawcroft
2012-10-26 10:17 ` James Greenhalgh
2012-11-12 12:00 ` James Greenhalgh
2012-11-19 9:51 ` James Greenhalgh [this message]
2012-11-19 18:36 ` Marcus Shawcroft
2012-11-28 11:07 ` [Patch AArch64-4.7] Backport - " James Greenhalgh
2012-11-29 15:11 ` Marcus Shawcroft
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='000601cdc63b$5cb49100$161db300$@greenhalgh@arm.com' \
--to=james.greenhalgh@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=gcc-patches@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).