From: Kirill Yukhin <kirill.yukhin@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>,
"H.J. Lu" <hjl.tools@gmail.com>, Uros Bizjak <ubizjak@gmail.com>
Subject: Re: [PATCH, test, i386] Fix for PR50155
Date: Mon, 22 Aug 2011 20:42:00 -0000 [thread overview]
Message-ID: <CAGs3Rfs-81y6oSknzOLPSa58Jx0dOXrh-v82JbdJ1329pp-DNw@mail.gmail.com> (raw)
In-Reply-To: <20110822191243.GB2687@tyan-ft48-01.lab.bos.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 627 bytes --]
Thanks for inputs.
Updated test attached.
K
On Mon, Aug 22, 2011 at 11:12 PM, Jakub Jelinek <jakub@redhat.com> wrote:
> On Mon, Aug 22, 2011 at 10:51:19PM +0400, Kirill Yukhin wrote:
>> testsuite/ChangeLog entry:
>> 2011-08-22 Kirill Yukhin <kirill.yukhin@intel.com>
>>
>> PR target/50155
>> * gcc.target/i386/pr50155.c: New test.
>
> For the testcase, I think you want explicit -mno-avx2 if
> you want to check that vpaddd hasn't been emitted, otherwise
> anybody testing with --with-arch=corei7-avx2 tuned compiler
> ot --target_board=unix/-mavx2 will see failures.
>
> Jakub
>
[-- Attachment #2: pr50155.test.patch --]
[-- Type: application/octet-stream, Size: 491 bytes --]
diff --git a/gcc/testsuite/gcc.target/i386/pr50155.c b/gcc/testsuite/gcc.target/i386/pr50155.c
new file mode 100644
index 0000000..c641d4c
--- /dev/null
+++ b/gcc/testsuite/gcc.target/i386/pr50155.c
@@ -0,0 +1,13 @@
+/* { dg-do compile } */
+/* { dg-options "-O3 -mavx -mno-avx2" } */
+
+void
+foo (int x, double *a, double *b, double c)
+{
+ int i;
+
+ for (i = 0; i < x; i++)
+ *a++ = *b++ * i / c;
+}
+
+/* { dg-final { scan-assembler-not "vpaddd\[ \\t\]+\[^\n\]*%ymm\[0-9\]" } } */
next prev parent reply other threads:[~2011-08-22 19:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 19:09 Kirill Yukhin
2011-08-22 19:51 ` Uros Bizjak
2011-08-22 20:36 ` Jakub Jelinek
2011-08-22 20:42 ` Kirill Yukhin [this message]
2011-08-22 23:04 ` Uros Bizjak
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=CAGs3Rfs-81y6oSknzOLPSa58Jx0dOXrh-v82JbdJ1329pp-DNw@mail.gmail.com \
--to=kirill.yukhin@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=jakub@redhat.com \
--cc=ubizjak@gmail.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).