This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH, Fortran] DEC Compatibility: New I/O Specifiers CARRIAGECONTROL, READONLY, SHARE with -fdec


On Thu, Oct 27, 2016 at 8:52 AM, Jakub Jelinek <jakub@redhat.com> wrote:
> On Thu, Oct 27, 2016 at 08:49:42AM -0400, Fritz Reese wrote:
>>
>> Do you know if there is there any way from DG to verify that a runtime
>> warning is emitted?
>
> Use dg-output for that.  And, if the test is supposed to exit with non-zero
> exit status because of the runtime error, then also dg-shouldfail.
>
>         Jakub

Thanks. I could never find good documentation on the various dg-*
testing options. I was browsing other test files to figure out how to
express dec_io_5 and dec_io_6. I first saw "XFAIL", I assumed it meant
"eXpected FAIL", and used it since I "expected" dec_io_5 to "fail" at
runtime. I was only half-right...

The attached should be correct now

---
Fritz Reese.

From: Fritz Reese <fritzoreese@gmail.com>
Date: Thu, 27 Oct 2016 08:46:33 -0400
Subject: [PATCH] Fix some DEC I/O testcases.

        gcc/testsuite/gfortran.dg/
        * dec_io_5.f90, dec_io_6.f90: Don't use "test.txt", and use
        dg-shouldfail/dg-output instead of XFAIL.
---
 gcc/testsuite/gfortran.dg/dec_io_5.f90 |    8 +++++---
 gcc/testsuite/gfortran.dg/dec_io_6.f90 |   22 ++++++++++++++++++----
 2 files changed, 23 insertions(+), 7 deletions(-)

Attachment: dec_io_testfix_3.diff
Description: Text document


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]