public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r11-8204] gcc.dg/pr84877.c: Xfail for cris-*-*
Date: Thu, 15 Apr 2021 20:36:54 +0000 (GMT)	[thread overview]
Message-ID: <20210415203654.551E9396E854@sourceware.org> (raw)

https://gcc.gnu.org/g:58fe131b91007793c0f12f5fe6cab3f1a017d0fa

commit r11-8204-g58fe131b91007793c0f12f5fe6cab3f1a017d0fa
Author: Hans-Peter Nilsson <hp@axis.com>
Date:   Thu Apr 15 21:51:08 2021 +0200

    gcc.dg/pr84877.c: Xfail for cris-*-*
    
    Unfortunately it appears that this PR is on nobody's radar.
    Xfailing it to get an arguably artificial zero regression
    state (since T0=2007-01-05) helps my autotester.
    
    Caveat: the pass/fail state of this test, as long as stack
    alignment isn't adjusted, is dependent on the alignment of
    the stack at the entry of main, so depending on the target,
    e.g. the size and number of environment variables at
    invocation time can affect the result (including simulator
    runs where environment variables are propagated to the
    target).
    
    gcc/testsuite:
            PR middle-end/84877
            * gcc.dg/pr84877.c: Xfail for cris-*-*.

Diff:
---
 gcc/testsuite/gcc.dg/pr84877.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.dg/pr84877.c b/gcc/testsuite/gcc.dg/pr84877.c
index 8a34dd4fb66..8551d27bcbb 100644
--- a/gcc/testsuite/gcc.dg/pr84877.c
+++ b/gcc/testsuite/gcc.dg/pr84877.c
@@ -1,4 +1,4 @@
-/* { dg-do run } */
+/* { dg-do run { xfail { cris-*-* } } } */
 /* { dg-options "-O2" } */
 
 #include <inttypes.h>


                 reply	other threads:[~2021-04-15 20:36 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=20210415203654.551E9396E854@sourceware.org \
    --to=hp@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).