This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PING^3 [ARM] [1/3] Refactor NEON builtin code
- From: Julian Brown <julian at codesourcery dot com>
- To: Jie Zhang <jie at codesourcery dot com>
- Cc: gcc-patches at gcc dot gnu dot org, Richard Earnshaw <Richard dot Earnshaw at arm dot com>
- Date: Wed, 19 Jan 2011 21:38:21 +0000
- Subject: Re: PING^3 [ARM] [1/3] Refactor NEON builtin code
- References: <4D135366.3050904@codesourcery.com> <4D2A7528.7060702@codesourcery.com> <4D33A219.7060908@codesourcery.com>
Hi,
On Mon, 17 Jan 2011 09:57:45 +0800
Jie Zhang <jie@codesourcery.com> wrote:
> > On 12/23/2010 09:49 PM, Jie Zhang wrote:
> >> http://gcc.gnu.org/ml/gcc-patches/2010-10/msg00851.html
> >>
> >> I just updated the patch to the latest trunk.
I can't approve/disapprove this patch, but this part makes me nervous:
IIUC it means that the builtins will depend on the order of patterns in
neon.md, which seems like a potential maintenance nightmare. I think it
also means that we depend on the order in which mode iterators get
expanded, which I strongly suspect isn't specified anywhere.
Can we avoid making that linkage?
Cheers,
Julian