From: Ramana Radhakrishnan <ramrad01@arm.com>
To: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: Re: [PATCH][ARM][1/3] Add vectorization support for rounding functions
Date: Wed, 06 Feb 2013 09:57:00 -0000 [thread overview]
Message-ID: <511228F0.20300@arm.com> (raw)
In-Reply-To: <002201cddd24$46f624f0$d4e26ed0$@tkachov@arm.com>
On 12/18/12 13:33, Kyrylo Tkachov wrote:
> Hi all,
>
> This patch does some refactoring by moving the definitions of the NEON
> builtins to a separate file (arm_neon_builtins.def) and includes that when
> initialising the neon_builtin_data array and also during
> the definition of enum arm_builtins (with appropriate redefinitions of the
> VAR* macros). This allows us to have symbolic names for the neon builtins
> that allows us to look up their declaration in
> arm_builtin_decls. This is needed for vectorisation support in the next
> patch. The ARM_BUILTIN_NEON_BASE constant which was defined as part of the
> arm_builtins enum is now defined as a macro, since
> various functions that deal with the initialisation and expansion of
> builtins use it.
>
> No regressions on arm-none-eabi with model.
>
> Ok for trunk?
>
> Thanks,
> Kyrill
>
>
> gcc/ChangeLog
>
> 2012-12-18 Kyrylo Tkachov <kyrylo.tkachov at arm.com>
>
> * config/arm/arm_neon_builtins.def: New file.
> * config/arm/arm.c (neon_builtin_data): Move contents to
> arm_neon_builtins.def.
> (enum arm_builtins): Include neon builtin definitions.
> (ARM_BUILTIN_NEON_BASE): Move from enum to macro.
>
arm.o in t-arm needs to depend on this new file. Otherwise OK for stage1 .
regards,
Ramana
prev parent reply other threads:[~2013-02-06 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 13:34 Kyrylo Tkachov
2013-01-07 10:35 ` Kyrylo Tkachov
2013-01-14 17:32 ` Kyrylo Tkachov
2013-01-22 17:10 ` Kyrylo Tkachov
2013-02-05 14:10 ` Kyrylo Tkachov
2013-02-06 9:57 ` Ramana Radhakrishnan [this message]
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=511228F0.20300@arm.com \
--to=ramrad01@arm.com \
--cc=Kyrylo.Tkachov@arm.com \
--cc=Richard.Earnshaw@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).