From: Eric Botcazou <ebotcazou@adacore.com>
To: gcc-patches@gcc.gnu.org
Subject: Fix PR testsuite/33033
Date: Wed, 12 Jan 2011 11:15:00 -0000 [thread overview]
Message-ID: <201101121154.28286.ebotcazou@adacore.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 361 bytes --]
This is a long-standing glitch visible in the results on SPARC64/Linux when
you configure --with-cpu=v8. Fixed by using the kludge from gcc.dg/sync-2.c.
Tested on SPARC64/Solaris, applied on all active branches.
2011-01-12 Eric Botcazou <ebotcazou@adacore.com>
PR testsuite/33033
* gcc.dg/20061124-1.c: Pass -mcpu=v9 on the SPARC.
--
Eric Botcazou
[-- Attachment #2: p.diff --]
[-- Type: text/x-diff, Size: 432 bytes --]
Index: gcc.dg/20061124-1.c
===================================================================
--- gcc.dg/20061124-1.c (revision 168632)
+++ gcc.dg/20061124-1.c (working copy)
@@ -1,5 +1,6 @@
/* { dg-do run } */
/* { dg-require-effective-target sync_char_short } */
+/* { dg-options "-mcpu=v9" { target sparc*-*-* } } */
/* This testcase failed on s390 because no compare instruction for
the check of FLAG was emitted. */
reply other threads:[~2011-01-12 10:55 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=201101121154.28286.ebotcazou@adacore.com \
--to=ebotcazou@adacore.com \
--cc=gcc-patches@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).