public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Roger Sayle <sayle@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-2651] [Committed] Tweak new test case gcc.target/i386/dec-cmov-2.c
Date: Sat, 31 Jul 2021 10:09:56 +0000 (GMT)	[thread overview]
Message-ID: <20210731100956.B92DB385801E@sourceware.org> (raw)

https://gcc.gnu.org/g:4c4249b71de3b15ba1e176ce90a57fb7bc54b917

commit r12-2651-g4c4249b71de3b15ba1e176ce90a57fb7bc54b917
Author: Roger Sayle <roger@nextmovesoftware.com>
Date:   Sat Jul 31 11:06:22 2021 +0100

    [Committed] Tweak new test case gcc.target/i386/dec-cmov-2.c
    
    With -m32, this test case is sensitive to the instruction timings of
    the target (for ifcvt to normalize bar() to foo() during the ce1 pass,
    prior to the transformations actually being tested here).  Specifying
    -march=core2 prevents these failures.  Committed as obvious.
    
    2021-07-31  Roger Sayle  <roger@nextmovesoftware.com>
    
    gcc/testsuite/ChangeLog
            * gcc.target/i386/dec-cmov-2.c: Require -march=core2 with -m32.

Diff:
---
 gcc/testsuite/gcc.target/i386/dec-cmov-2.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.target/i386/dec-cmov-2.c b/gcc/testsuite/gcc.target/i386/dec-cmov-2.c
index 115db992f39..9fbccc36f82 100644
--- a/gcc/testsuite/gcc.target/i386/dec-cmov-2.c
+++ b/gcc/testsuite/gcc.target/i386/dec-cmov-2.c
@@ -1,6 +1,6 @@
 /* { dg-do compile } */
 /* { dg-options "-O2" } */
-/* { dg-additional-options "-march=pentiumpro -mregparm=3" { target ia32 } } */
+/* { dg-additional-options "-march=core2 -mregparm=3" { target ia32 } } */
 
 int foo(int x)
 {


                 reply	other threads:[~2021-07-31 10:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210731100956.B92DB385801E@sourceware.org \
    --to=sayle@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /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).