From: Jakub Jelinek <jakub@redhat.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, i386]: Add target i?86-*-* to many tests
Date: Mon, 10 Nov 2014 23:15:00 -0000 [thread overview]
Message-ID: <20141110231414.GS5026@tucnak.redhat.com> (raw)
In-Reply-To: <CAFULd4akVuu2sWmCVwJvJanXdDbss4+=5f8yehL9joe+rGc7bw@mail.gmail.com>
On Sun, Nov 02, 2014 at 08:31:43PM +0100, Uros Bizjak wrote:
> Attached (mechanical) patch adds i?86-*-* target to many tests, where
> only x86_64-*-* is listed. Please note that x86_64-*-* already
> included && lp64 for 64bit specific tests due to -m32 multilib
> testing.
>
> 2014-11-02 Uros Bizjak <ubizjak@gmail.com>
>
> * c-c++-common/ubsan/float-cast-overflow-6.c: Add i?86-*-* target.
...
> * gcc.dg/tm/memopt-15.c: Ditto.
>
> Tested on x86_64-linux-gnu {,-m32} and committed to mainline SVN.
>
> I will keep an eye on autotesters for possible fallout.
This regressed on i686-linux in memopt-15.c, because without -msse2
there is psABI warning. Rather than adding -Wno-psabi, I chose to
add -msse2, the test is dg-do compile, so we don't need any extra as
or runtime support.
Committed as obvious after bootstrap/regtest on x86_64-linux and i686-linux.
2014-11-11 Jakub Jelinek <jakub@redhat.com>
* gcc.dg/tm/memopt-15.c: Add -msse2 to dg-options.
--- gcc/testsuite/gcc.dg/tm/memopt-15.c.jj 2014-11-10 19:16:09.609635932 +0100
+++ gcc/testsuite/gcc.dg/tm/memopt-15.c 2014-11-10 22:24:42.740667616 +0100
@@ -1,5 +1,5 @@
/* { dg-do compile { target { i?86-*-linux* x86_64-*-linux* } } } */
-/* { dg-options "-fgnu-tm -O" } */
+/* { dg-options "-fgnu-tm -O -msse2" } */
/* Test the TM vector logging functions. */
Jakub
prev parent reply other threads:[~2014-11-10 23:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 19:31 Uros Bizjak
2014-11-10 23:15 ` Jakub Jelinek [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=20141110231414.GS5026@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--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).