From: Marcus Shawcroft <marcus.shawcroft@gmail.com>
To: Kyrill Tkachov <kyrylo.tkachov@arm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [AArch64] Implement some vca*_f[32,64] intrinsics
Date: Thu, 17 Jul 2014 10:12:00 -0000 [thread overview]
Message-ID: <CAFqB+Pwhvg8TK6CJ6-cGTikeMpPLgbOVrWDihct5bgmSqkuSPQ@mail.gmail.com> (raw)
In-Reply-To: <53BE471B.5040203@arm.com>
On 10 July 2014 08:56, Kyrill Tkachov <kyrylo.tkachov@arm.com> wrote:
>
> On 02/07/14 08:59, Christophe Lyon wrote:
>>
>> Hi,
>>
>> It seems some of the scan-assembler directives fail:
>>
>> http://cbuild.validation.linaro.org/build/cross-validation/gcc/trunk/212196/aarch64-none-elf/diff-gcc-rh50-aarch64-none-elf-default-default-default.txt
>>
>> Christophe.
>
>
> This patch should fix the tests by marking the appropriate variable
> volatile.
> Sorry for the delay and breakage.
> Ok for trunk?
OK /Marcus
prev parent reply other threads:[~2014-07-17 10:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 14:30 Kyrill Tkachov
2014-06-30 13:33 ` Kyrill Tkachov
2014-07-01 12:13 ` Marcus Shawcroft
2014-07-02 8:00 ` Christophe Lyon
2014-07-02 8:02 ` Kyrill Tkachov
2014-07-10 7:56 ` Kyrill Tkachov
2014-07-17 10:12 ` Marcus Shawcroft [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=CAFqB+Pwhvg8TK6CJ6-cGTikeMpPLgbOVrWDihct5bgmSqkuSPQ@mail.gmail.com \
--to=marcus.shawcroft@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@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).