public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/35015] missing cleanup-modules directive in testsuite/gfortran*
Date: Sun, 03 Feb 2008 14:35:00 -0000	[thread overview]
Message-ID: <20080203143444.500.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35015-11811@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from fxcoudert at gcc dot gnu dot org  2008-02-03 14:34 -------
(In reply to comment #5)
> In the event that we can check against several multilib variants (?) that thus
> match different dg-require (?), we may (?) eventually check against stale
> module data if a "board" does not cleanup-modules after itself and each board
> is run in the same directory (where an old multilib-run may have left old
> output/modules), no?

I don't think so, since each a newer version of the module file is written
every time before being read. It still would be nice to have to way to support
a cleanup directive in the gfortran.fortran-torture/ directory.


-- 

fxcoudert at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fxcoudert at gcc dot gnu dot
                   |                            |org
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2008-02-03 14:34:44
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35015


  parent reply	other threads:[~2008-02-03 14:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-29 14:25 [Bug fortran/35015] New: " aldot at gcc dot gnu dot org
2008-01-29 15:57 ` [Bug fortran/35015] " burnus at gcc dot gnu dot org
2008-01-29 17:10 ` aldot at gcc dot gnu dot org
2008-01-29 20:35 ` burnus at gcc dot gnu dot org
2008-01-29 21:03 ` rep dot dot dot nop at gmail dot com
2008-01-29 21:57 ` aldot at gcc dot gnu dot org
2008-02-03 14:35 ` fxcoudert at gcc dot gnu dot org [this message]
2009-01-03 22:48 ` dfranke at gcc dot gnu dot org
     [not found] <bug-35015-4@http.gcc.gnu.org/bugzilla/>
2012-03-02  7:57 ` aldot at gcc dot gnu.org
2012-06-01 12:44 ` burnus at gcc dot gnu.org

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=20080203143444.500.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).