public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: mrs@wrs.com (Mike Stump)
To: egcs@cygnus.com
Subject: execution test fails - XFAIL powerpc-*-eabi
Date: Wed, 05 Nov 1997 18:31:00 -0000	[thread overview]
Message-ID: <199711060228.SAA05969@kankakee.wrs.com> (raw)

To the author of execution test fails - XFAIL powerpc-*-eabi in
g++.mike/dyncast[12].C, it doesn't do what you think it does.  You
have to add support for XFAIL, if you want to use it.

But caution, I tried to add it for you, and got caught in the old
semantics games.  What we appear to want, is a execution test - XFAIL
powerpc-*-eabi in this case, and then add support for that.  The
reason is we don't want universal complement target triplets in the
common case (because we don't have them), and we want execution test
fails - to, by default, setup an expected failure for all machines.

I think we should do something like the below in the meantime.  This
gets rid of the xpass for those two cases on most machines.

Doing diffs in testsuite:
*** testsuite/g++.old-deja/g++.mike/dyncast1.C.~1~	Wed Oct 29 16:07:54 1997
--- testsuite/g++.old-deja/g++.mike/dyncast1.C	Wed Nov  5 18:09:42 1997
***************
*** 1,6 ****
  // Special g++ Options: -fexceptions -w
  // excess errors test - XFAIL a29k-*-* sparc64-*-elf sh-*-* arm-*-pe
- // execution test fails - XFAIL powerpc-*-eabi
  
  #include <typeinfo>
  
--- 1,5 ----
*** testsuite/g++.old-deja/g++.mike/dyncast2.C.~1~	Wed Oct 29 16:07:55 1997
--- testsuite/g++.old-deja/g++.mike/dyncast2.C	Wed Nov  5 18:09:45 1997
***************
*** 1,6 ****
  // Special g++ Options: -fexceptions -w
  // excess errors test - XFAIL a29k-*-* sparc64-*-elf sh-*-* arm-*-pe
- // execution test fails - XFAIL powerpc-*-eabi
  
  // Ensure reference handling works.
  
--- 1,5 ----
--------------

                 reply	other threads:[~1997-11-05 18:31 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=199711060228.SAA05969@kankakee.wrs.com \
    --to=mrs@wrs.com \
    --cc=egcs@cygnus.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).