From: Janis Johnson <janis_johnson@mentor.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: <christophe.lyon@st.com>
Subject: [testsuite] fix ARM test gcc.target/arm/neon-vld1_dupQ.c
Date: Mon, 14 Jan 2013 23:02:00 -0000 [thread overview]
Message-ID: <50F48EF9.1010206@mentor.com> (raw)
Test gcc.target/arm/neon-vld1_dupQ.c started failing with r194594, a C
front end change that causes the test to get warnings. The test passes
local variables of type int64x1_t to functions declared with arguments
of type int64_t. This patch casts the values passed to those arguments.
It's possible that the patch invalidates the intent of the test, so I've
copied the test's author.
OK for trunk?
Janis
next reply other threads:[~2013-01-14 23:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 23:02 Janis Johnson [this message]
2013-01-15 16:29 ` Janis Johnson
2013-01-17 12:44 ` Christophe Lyon
2013-01-22 10:52 ` Ramana Radhakrishnan
2013-01-16 13:46 Nick Clifton
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=50F48EF9.1010206@mentor.com \
--to=janis_johnson@mentor.com \
--cc=christophe.lyon@st.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=janisjo@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).