From: Yufeng Zhang <yufengzhangdev@gmail.com>
To: Tejas Belagod <tbelagod@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Marc Glisse <marc.glisse@inria.fr>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>
Subject: Re: [Patch, AArch64] Restructure arm_neon.h vector types' implementation.
Date: Wed, 25 Jun 2014 08:31:00 -0000 [thread overview]
Message-ID: <CAHkEkXq36voJ_7PCn+_1LU5x8-31=pWc=r+JO1x92w8VtvsDEA@mail.gmail.com> (raw)
In-Reply-To: <53A84C27.9050001@arm.com>
On 23 June 2014 16:47, Tejas Belagod <tbelagod@arm.com> wrote:
>
> Hi,
>
> Here is a patch that restructures neon builtins to use vector types based on
> standard base types. We previously defined arm_neon.h's neon vector
> types(int8x8_t) using gcc's front-end vector extensions. We now move away
> from that and use types built internally(e.g. __Int8x8_t). These internal
> types names are defined by the AAPCS64 and we build arm_neon.h's public
> vector types over these internal types. e.g.
>
> typedef __Int8x8_t int8x8_t;
>
> as opposed to
>
> typedef __builtin_aarch64_simd_qi int8x8_t
> __attribute__ ((__vector_size__ (8)));
>
> Impact on mangling:
>
> This patch does away with these builtin scalar types that the vector types
> were based on. These were previously used to look up mangling names. We now
> use the internal vector type names(e.g. __Int8x8_t) to lookup mangling for
> the arm_neon.h-exported vector types. There are a few internal scalar
> types(__builtin_aarch64_simd_oi etc.) that is needed to efficiently
> implement some NEON Intrinsics. These will be declared in the back-end and
> registered in the front-end and aarch64-specific builtin types, but are not
> user-visible. These, along with a few scalar __builtin types that aren't
> user-visible will have implementation-defined mangling. Because we don't
> have strong-typing across all builtins yet, we still have to maintain the
> old builtin scalar types - they will be removed once we move over to a
> strongly-typed builtin system implemented by the qualifier infrastructure.
>
> Marc Glisse's patch in this thread exposed this issue
> https://gcc.gnu.org/ml/gcc-patches/2014-04/msg00618.html. I've tested my
> patch with the change that his patch introduced, and it seems to work fine -
> specifically these two lines:
>
> + for (tree t = registered_builtin_types; t; t = TREE_CHAIN (t))
> + emit_support_tinfo_1 (TREE_VALUE (t));
>
> Regressed on aarch64-none-elf. OK for trunk?
>
> Thanks,
> Tejas.
>
> gcc/Changelog
>
> 2014-06-23 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_types,
> 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_fold_builtin): Remove redundant defn.
> (aarch64_init_crc32_builtins): Use aarch64_simd_builtin_std_type.
> * config/aarch64/aarch64-simd-builtin-types.def: New.
Has the content of this new file been included in the patch?
Yufeng
next prev parent reply other threads:[~2014-06-25 8:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 15:48 Tejas Belagod
2014-06-25 8:31 ` Yufeng Zhang [this message]
2014-06-27 15:32 ` Tejas Belagod
2014-06-27 16:01 ` Yufeng Zhang
2014-08-22 12:02 ` Tejas Belagod
2014-07-04 14:27 ` James Greenhalgh
2014-08-22 12:07 ` Tejas Belagod
2014-07-08 16:00 ` James Greenhalgh
2014-06-28 10:25 ` Marc Glisse
2014-08-22 11:59 ` Tejas Belagod
2014-08-22 12:54 ` 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='CAHkEkXq36voJ_7PCn+_1LU5x8-31=pWc=r+JO1x92w8VtvsDEA@mail.gmail.com' \
--to=yufengzhangdev@gmail.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=marc.glisse@inria.fr \
--cc=tbelagod@arm.com \
/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).