public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Lee Millward" <lee.millward@gmail.com>
To: "Tobias Burnus" <burnus@ph2.uni-koeln.de>
Cc: fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re:
Date: Fri, 06 Jul 2007 08:17:00 -0000	[thread overview]
Message-ID: <9784d3ab0707060116u70d09b97nae768647a05d5fc1@mail.gmail.com> (raw)
In-Reply-To: <12337.212.202.24.200.1183703263.squirrel@www.webmail.uni-koeln.de>

Hi Tobias,

On 7/6/07, Tobias Burnus <burnus@ph2.uni-koeln.de> wrote:
> Hi Lee,
>
> I only glanced at your patch.
>
> Lee Millward wrote:
> > * gfortran.dg/cmplx_intrinsic_1.f90
> >       * gfortran.dg/pr32222.f90: New test.
> >       * gfortran.dg/pr32238.f90: New test.
> >       * gfortran.dg/pr32242.f90: New test
>
> You miss something like
> ! { dg-do run }
> or
> ! { dg-do compile }

Isn't this on by default?

> For those test cases with modules, you should add
>
> ! { dg-final { cleanup-modules "MODULE_NAME" } }
>
> to delete the .mod files after compilation.
>

Thanks for that, I didn't know about that directive so I'll add it in
and retest.

Cheers,
Lee.

  reply	other threads:[~2007-07-06  8:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06  6:27 Re: Tobias Burnus
2007-07-06  8:17 ` Lee Millward [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-22 13:06 Mamadou Diop
2023-08-23  8:19 ` Arjen Markus
2021-03-10 18:34 mscfd
2021-03-11  7:48 ` Richard Biener
2020-07-26  4:49 Damian Rouson
2020-07-26  8:55 ` Arjen Markus
2013-03-13  5:51 Re: DavidLNewton
2013-03-12  9:22 Re: DavidLNewton
     [not found] <8C94B5ACA298987-8B4-8502@WEBMAIL-DB13.sysops.aol.com>
2007-04-12 21:00 ` Re: FX Coudert
2007-03-27 13:13 Re: Paul Richard Thomas
     [not found] <4195D82C2DB1D211B9910008C7C9B06F01F373E0@lr0nt3.lr.tudelft.nl>
2003-12-07 14:17 ` Re: Paul Brook

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=9784d3ab0707060116u70d09b97nae768647a05d5fc1@mail.gmail.com \
    --to=lee.millward@gmail.com \
    --cc=burnus@ph2.uni-koeln.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).