From: Marcus Shawcroft <marcus.shawcroft@gmail.com>
To: Ian Bolton <ian.bolton@arm.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, AArch64] Fix macro in vdup_lane_2 test case
Date: Mon, 19 May 2014 10:44:00 -0000 [thread overview]
Message-ID: <CAFqB+PyH_=uCaiQ=HOWEzcPAh=atGFmXunn7dNGC2o4s-4Q71g@mail.gmail.com> (raw)
In-Reply-To: <536bc1d0.a2a1440a.3499.ffffeb33SMTPIN_ADDED_BROKEN@mx.google.com>
On 8 May 2014 18:41, Ian Bolton <ian.bolton@arm.com> wrote:
> gcc/testsuite
> * gcc.target/aarch64/vdup_lane_2.c (force_simd): Emit an
> actual instruction to move into the allocated register.
This macro is attempting to force a value to a particular class of
register, we don't need or want the mov instruction at all. Isn't
something like this sufficient:
#define force_simd(V1) asm volatile ("" \
: "+w"(V1) \
: \
: /* No clobbers */)
?
/Marcus
next parent reply other threads:[~2014-05-19 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <536bc1d0.a2a1440a.3499.ffffeb33SMTPIN_ADDED_BROKEN@mx.google.com>
2014-05-19 10:44 ` Marcus Shawcroft [this message]
2014-05-20 10:36 ` Ian Bolton
2014-05-08 17:41 Ian Bolton
2014-05-16 9:20 ` Ian Bolton
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='CAFqB+PyH_=uCaiQ=HOWEzcPAh=atGFmXunn7dNGC2o4s-4Q71g@mail.gmail.com' \
--to=marcus.shawcroft@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ian.bolton@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).