From: Richard Earnshaw <rearnsha@arm.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Julian Brown <julian@codesourcery.com>,
Ira Rosen <IRAR@il.ibm.com>,
gcc-patches@gcc.gnu.org, paul@codesourcery.com,
eres@il.ibm.com
Subject: Re: [PATCH, ARM] Misaligned access support for ARM Neon
Date: Mon, 30 Nov 2009 14:15:00 -0000 [thread overview]
Message-ID: <1259590445.6000.25.camel@e200601-lin.cambridge.arm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0911301400131.10438@digraph.polyomino.org.uk>
On Mon, 2009-11-30 at 14:01 +0000, Joseph S. Myers wrote:
> On Mon, 30 Nov 2009, Julian Brown wrote:
>
> > I've also drafted a bit of hopefully-explanatory text in md.texi about
> > movmisalign<mode> and element ordering.
>
> Texinfo markup fixes: ``opaque'', @code{TARGET_VECTOR_ALWAYS_MISALIGN}.
> The two new target hooks TARGET_VECTOR_ALWAYS_MISALIGN and
> TARGET_VECTOR_MIN_ALIGNMENT also need documentation in tm.texi.
>
I can't say I like this particular way of describing Neon. It seems to
me that what's really needed is for the vectorizer to have an equivalent
concept for vector elements to the TARGET_WORDS_BIG_ENDIAN -- namely
TARGET_VECT_ELEMENTS_BIG_ENDIAN -- on Neon this would always be false.
R.
next prev parent reply other threads:[~2009-11-30 14:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 17:21 Julian Brown
2009-11-18 12:03 ` Ira Rosen
2009-11-30 13:53 ` Julian Brown
2009-11-30 14:03 ` Joseph S. Myers
2009-11-30 14:15 ` Richard Earnshaw [this message]
2009-11-30 14:33 ` Paul Brook
2009-11-30 15:06 ` Richard Earnshaw
2009-12-18 18:09 ` Julian Brown
2009-12-21 8:44 ` Ira Rosen
2009-12-21 15:35 ` Paul Brook
2010-05-18 0:44 ` Julian Brown
2010-05-18 8:50 ` Ira Rosen
2010-05-18 15:58 ` Julian Brown
2010-06-04 12:50 ` Julian Brown
2010-06-04 16:26 ` Richard Earnshaw
2010-06-05 14:39 ` Joseph S. Myers
2010-06-07 19:09 ` Julian Brown
2010-06-08 15:25 ` Mark Mitchell
2010-08-03 16:32 ` Julian Brown
2010-08-04 6:38 ` Ira Rosen
2010-09-23 9:49 ` Richard Earnshaw
2010-10-04 15:00 ` Julian Brown
2010-10-07 13:06 ` Ramana Radhakrishnan
2009-11-30 15:43 ` Joseph S. Myers
2009-12-01 8:39 ` Ira Rosen
2009-11-18 14:25 ` Paul Brook
2009-12-03 15:12 Plotnikov Dmitry
2009-12-03 16:57 ` Richard Guenther
2009-12-04 14:40 ` Plotnikov Dmitry
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=1259590445.6000.25.camel@e200601-lin.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=IRAR@il.ibm.com \
--cc=eres@il.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=julian@codesourcery.com \
--cc=paul@codesourcery.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).