From: Uros Bizjak <ubizjak@gmail.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Vladimir Makarov <vmakarov@redhat.com>, "H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: patch to fix PR60969
Date: Sat, 17 May 2014 11:00:00 -0000 [thread overview]
Message-ID: <CAFULd4YfXv55guVQnF8nZWx8WwmiLyCR1qH9T6trMXnRJn91rg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]
Hello!
Attached patch enhances the testcase to also check for presence of MMX
registers on all 32bit x86 targets.
2014-05-17 Uros Bizjak <ubizjak@gmail.com>
* g++.dg/pr60969.C: Compile for all ilp32 x86 targets.
(dg-options): Add -mfpmath=387.
(dg-final): Check that no MMX registers are used.
Tested on x86-64-pc-linux-gnu {,-m32} and committed to mainline and 4.9 branch.
Uros.
[-- Attachment #2: t.diff.txt --]
[-- Type: text/plain, Size: 522 bytes --]
Index: pr60969.C
===================================================================
--- pr60969.C (revision 210549)
+++ pr60969.C (working copy)
@@ -1,5 +1,5 @@
-/* { dg-do compile { target i?86-*-* } } */
-/* { dg-options "-O2 -ftree-vectorize -march=pentium4" } */
+/* { dg-do compile { target { { i?86-*-* x86_64-*-* } && ilp32 } } } */
+/* { dg-options "-O2 -ftree-vectorize -march=pentium4 -mfpmath=387" } */
struct A
{
@@ -28,3 +28,5 @@
}
return x;
}
+
+/* { dg-final { scan-assembler-not "%mm" } } */
next reply other threads:[~2014-05-17 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 11:00 Uros Bizjak [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-16 17:49 Vladimir Makarov
2014-05-19 21:37 ` James Greenhalgh
2014-05-20 0:25 ` H.J. Lu
2014-05-20 14:37 ` Vladimir Makarov
2014-05-22 9:18 ` Ramana Radhakrishnan
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=CAFULd4YfXv55guVQnF8nZWx8WwmiLyCR1qH9T6trMXnRJn91rg@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=vmakarov@redhat.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).