From: James Greenhalgh <james.greenhalgh@arm.com>
To: Marc Glisse <marc.glisse@inria.fr>
Cc: Tejas Belagod <Tejas.Belagod@arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [AArch64, Patch] Restructure arm_neon.h vector types's implementation(Take 2).
Date: Wed, 05 Nov 2014 23:31:00 -0000 [thread overview]
Message-ID: <20141105233124.GA29096@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1411052236160.1572@laptop-mg.saclay.inria.fr>
On Wed, Nov 05, 2014 at 09:50:52PM +0000, Marc Glisse wrote:
> On Wed, 5 Nov 2014, Tejas Belagod wrote:
>
> >>> 2014-10-01 Tejas Belagod <tejas.belagod@arm.com>
> >>>
> >>> * config/aarch64/aarch64-builtins.c
> >>> (aarch64_build_scalar_type): Remove.
> >>> (aarch64_scalar_builtin_types, aarch64_simd_type,
> >>> aarch64_simd_type, aarch64_mangle_builtin_scalar_type,
> >>> aarch64_mangle_builtin_vector_type,
> >>> aarch64_mangle_builtin_type, aarch64_simd_builtin_std_type,
> >>> aarch64_lookup_simd_builtin_type, aarch64_simd_builtin_type,
> >>> aarch64_init_simd_builtin_types,
> >>> aarch64_init_simd_builtin_scalar_types): New.
> >>> (aarch64_init_simd_builtins): Refactor.
> >>> (aarch64_init_crc32_builtins): Fixup with qualifier.
> >>> * config/aarch64/aarch64-protos.h
> >>> (aarch64_mangle_builtin_type): Export.
> >>> * config/aarch64/aarch64-simd-builtin-types.def: New.
> >>> * config/aarch64/aarch64.c (aarch64_simd_mangle_map): Remove.
> >>> (aarch64_mangle_type): Refactor.
> >>> * config/aarch64/arm_neon.h: Declare vector types based on
> >>> internal types.
> >>> * config/aarch64/t-aarch64: Update dependency.
> >>
> >> OK /Marcus
> >
> > Thanks. Rebased, retested on aarch64-none-elf and committed as r217114.
>
> Thanks. Do you know if anyone is planning to "port" this patch to the arm
> target (which IIRC has the same issue)? No pressure, this is just so I
> know if I should ping the alternate __float128 patch or wait.
Hi Marc,
Yes, you're right, the arm target also has this issue. I have a port of
Tejas' patch based on top of some other refactoring of the arm
target's builtin infrastructure I've been working on - I'm hoping to get
that all rebased and proposed upstream in the next couple of weeks.
Thanks,
James
next prev parent reply other threads:[~2014-11-05 23:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 8:26 Tejas Belagod
2014-11-03 16:49 ` Marcus Shawcroft
2014-11-05 8:28 ` Tejas Belagod
2014-11-05 8:53 ` Tejas Belagod
2014-11-05 21:50 ` Marc Glisse
2014-11-05 23:31 ` James Greenhalgh [this message]
2014-11-18 10:33 ` James Greenhalgh
2014-11-18 21:09 ` Marc Glisse
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=20141105233124.GA29096@arm.com \
--to=james.greenhalgh@arm.com \
--cc=Tejas.Belagod@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=marc.glisse@inria.fr \
/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).