From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: gcc-patches@gcc.gnu.org
Cc: fortran@gcc.gnu.org
Subject: [testsuite, fortran] XFAIL gfortran.dg/execute_command_line_2.f90 (PR libfortran/67412)
Date: Tue, 01 Sep 2015 11:53:00 -0000 [thread overview]
Message-ID: <ydda8t6jqym.fsf@lokon.CeBiTec.Uni-Bielefeld.DE> (raw)
[-- Attachment #1: Type: text/plain, Size: 597 bytes --]
As discussed in the PR, gfortran.dg/execute_command_line_2.f90 execution
FAILs on Solaris 10 due to a bug in /bin/sh's exit code handling. Since
the fix is involved and the issue a corner case, we decided to XFAIL
execution instead (at least until an eventual fix is forthcoming).
Tested with the appropriate runtest invocations on i386-pc-solaris2.10
and i386-pc-solaris2.12, installed on mainline as pre-approved in the PR.
Rainer
2015-09-01 Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
PR libfortran/67412
* gfortran.dg/execute_command_line_2.f90: XFAIL execution on
*-*-solaris2.10.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: sol10-execute_command_line_2-xfail.patch --]
[-- Type: text/x-patch, Size: 562 bytes --]
# HG changeset patch
# Parent c91089a9a064d057d89d1b997b04e5cbac524137
XFAIL gfortran.dg/execute_command_line_2.f90 (PR libfortran/67412)
diff --git a/gcc/testsuite/gfortran.dg/execute_command_line_2.f90 b/gcc/testsuite/gfortran.dg/execute_command_line_2.f90
--- a/gcc/testsuite/gfortran.dg/execute_command_line_2.f90
+++ b/gcc/testsuite/gfortran.dg/execute_command_line_2.f90
@@ -1,4 +1,5 @@
! { dg-do run }
+! { dg-xfail-run-if "PR libfortran/67412" { *-*-solaris2.10 } }
!
! Check that EXECUTE_COMMAND_LINE handles invalid command lines appropriately
!
[-- Attachment #3: Type: text/plain, Size: 143 bytes --]
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
reply other threads:[~2015-09-01 11:53 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=ydda8t6jqym.fsf@lokon.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=fortran@gcc.gnu.org \
--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).