From: Paul Hua <paul.hua.gm@gmail.com>
To: gcc-patches@gcc.gnu.org
Cc: catherine_moore@mentor.com, matthew.fortune@imgtec.com
Subject: [PATCH][Testsuite] Fix mips dsp testsuite mistakes
Date: Sat, 21 May 2016 06:41:00 -0000 [thread overview]
Message-ID: <CAKjxQH=MD=5Z-XTpM4N8BYkW8wiKKQyiScUBHz4fy72hCq8nCw@mail.gmail.com> (raw)
Hi,
There are some mistakes in mips dsp testsuite.
This patch fixing it.
Ok to commit?
[mips] Fix mips dsp testsuite mistake.
gcc/testsuite/gcc.target/mips/
*mips32-dsp-run.c: Fix mistake.
Index: gcc/testsuite/ChangeLog
===================================================================
--- gcc/testsuite/ChangeLog (revision 236553)
+++ gcc/testsuite/ChangeLog (working copy)
@@ -1,3 +1,7 @@
+2016-05-21 Chenghua Xu <paul.hua.gm@gmail.com>
+
+ * gcc.target/mips/mips32-dsp-run.c: Fix mistake.
+
2016-05-20 Martin Sebor <msebor@redhat.com>
PR c/71115
Index: gcc/testsuite/gcc.target/mips/mips32-dsp-run.c
===================================================================
--- gcc/testsuite/gcc.target/mips/mips32-dsp-run.c (revision 236553)
+++ gcc/testsuite/gcc.target/mips/mips32-dsp-run.c (working copy)
@@ -394,7 +394,7 @@ NOMIPS16 void test_MIPS_DSP ()
v2q15_a = (v2q15) {0x1234, 0x5678};
i32_b = 1;
- v2q15_s = (v2q15) {0x2468, 0x7fff};
+ v2q15_s = (v2q15) {0x2468, 0xacf0};
v2q15_r = __builtin_mips_shll_s_ph (v2q15_a, i32_b);
r = (int) v2q15_r;
s = (int) v2q15_s;
@@ -409,7 +409,7 @@ NOMIPS16 void test_MIPS_DSP ()
q31_a = 0x70000000;
i32_b = 1;
- q31_s = 0x7fffffff;
+ q31_s = 0xe0000000;
q31_r = __builtin_mips_shll_s_w (q31_a, i32_b);
if (q31_r != q31_s)
abort ();
@@ -961,9 +961,9 @@ NOMIPS16 void test_MIPS_DSP ()
abort ();
#endif
- i32_a = 0x1357a468;
+ i32_a = 0x13572468;
__builtin_mips_wrdsp (i32_a, 63);
- i32_s = 0x03572428;
+ i32_s = 0x13572468;
i32_r = __builtin_mips_rddsp (63);
if (i32_r != i32_s)
abort ();
Regards,
Chenghua
next reply other threads:[~2016-05-21 6:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-21 6:41 Paul Hua [this message]
2016-05-21 7:05 ` Maciej W. Rozycki
2016-05-27 13:46 ` Paul Hua
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='CAKjxQH=MD=5Z-XTpM4N8BYkW8wiKKQyiScUBHz4fy72hCq8nCw@mail.gmail.com' \
--to=paul.hua.gm@gmail.com \
--cc=catherine_moore@mentor.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=matthew.fortune@imgtec.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).