This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran 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] | |
On Sat, Nov 04, 2006 at 12:36:27PM +0100, Bernhard Fischer wrote:
>On Thu, Nov 02, 2006 at 05:11:06PM -0800, Janis Johnson wrote:
>>On Thu, Nov 02, 2006 at 06:46:11PM +0100, Bernhard Fischer wrote:
>>> >It was not yet fixed nor committed due to problems with dejagnu.
>>> >See http://gcc.gnu.org/ml/gcc/2006-10/msg00408.html
>>> >
>>> >I'm rewriting the testcases (for free- and fixed form) now and want to
>>> >see if i can use dg-final { scan-assembler ".*" }.
>>
>>I figured out how to write procs output-exists and output-exists-not
>>that can be called from dg-final to verify whether or not the compiler
>>output file was not produced. Will that help?
>
>That would help, yes. I'd need this on trunk, the 4_2 and 4_1 branches
>if possible.
>
>Thanks!
What i did come up with was the attached, fwiw.
I did not (yet) look at how to distinguish dg-do modes, in order to get
the output_file extension right.
This works for me for
$ head -n 4 gcc/testsuite/gfortran.dg/warnings_are_errors_1.f
! { dg-do compile }
! { dg-options " -Werror" }
! { dg-final { output-exists-not } }
! PR fortran/21061
but i take it there is a more elegant way to do this.
Attachment:
gcc.testsuite.pr21061.00.diff
Description: Text document
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |