public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marcus Shawcroft <marcus.shawcroft@arm.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] [AArch64] Refactor Advanced SIMD builtin initialisation.
Date: Mon, 15 Oct 2012 11:35:00 -0000	[thread overview]
Message-ID: <507BF4D5.2080602@arm.com> (raw)
In-Reply-To: <1349452352-20980-1-git-send-email-james.greenhalgh@arm.com>

On 05/10/12 16:52, James Greenhalgh wrote:
>
> Hi,
>
> This patch refactors the initialisation code for the Advanced
> SIMD builtins under the AArch64 target. The patch has been
> regression tested on aarch64-none-elf.
>
> OK for aarch64-branch?
>
> (If yes, someone will have to commit this for me as I do not
> have commit rights)
>
> Thanks,
> James Greenhalgh
>
> ---
> 2012-09-07  James Greenhalgh<james.greenhalgh@arm.com>
> 	Tejas Belagod<tejas.belagod@arm.com>
>
> 	* config/aarch64/aarch64-builtins.c
> 	(aarch64_simd_builtin_type_bits): Rename to...
> 	(aarch64_simd_builtin_type_mode): ...this, make sequential.
> 	(aarch64_simd_builtin_datum): Refactor members where possible.
> 	(VAR1, VAR2, ..., VAR12): Update accordingly.
> 	(aarch64_simd_builtin_data): Update accordingly.
> 	(init_aarch64_simd_builtins): Refactor.
> 	(aarch64_simd_builtin_compare): Remove.
> 	(locate_simd_builtin_icode): Likewise.

OK and backport to aarch64-4.7-branch please.

/Marcus

  reply	other threads:[~2012-10-15 11:34 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 [this message]
2012-10-26 10:17   ` James Greenhalgh
2012-11-12 12:00   ` James Greenhalgh
2012-11-19  9:51     ` *ping* " James Greenhalgh
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=507BF4D5.2080602@arm.com \
    --to=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).