public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/50288] FAIL: gfortran.dg/class_45b.f03
Date: Sun, 04 Sep 2011 20:35:00 -0000	[thread overview]
Message-ID: <bug-50288-4-Fabl5Q7pMy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50288-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2011-09-04 20:35:36 UTC ---
> An evil trick would be the following, which causes a run once: ...

It works, but I think if this trick is used, it should be documented as in
gcc/testsuite/gfortran.dg/cray_pointers_2.f90:

! Using two spaces between dg-do and run is a hack to keep gfortran-dg-runtest
! from cycling through optimization options for this expensive test.

Another working possibility is to remove the line

! { dg-final { cleanup-modules "G_Nodes" } }

from gfortran.dg/class_45b.f03 and add an empty "cleaning" test:

cat ./gcc/testsuite/gfortran.dg/class_45c.f03

! { dg-do run }
!
! PR 50227: [4.7 Regression] [OOP] ICE-on-valid with allocatable class variable
!
! Contributed by Andrew Benson <abenson@caltech.edu>

program Test
end program Test

! { dg-final { cleanup-modules "G_Nodes" } }

Note that it will be impossible to test gfortran.dg/class_45b.f03 alone.


  parent reply	other threads:[~2011-09-04 20:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-04 18:49 [Bug fortran/50288] New: " hjl.tools at gmail dot com
2011-09-04 19:18 ` [Bug fortran/50288] " dominiq at lps dot ens.fr
2011-09-04 19:19 ` dominiq at lps dot ens.fr
2011-09-04 19:55 ` burnus at gcc dot gnu.org
2011-09-04 20:35 ` dominiq at lps dot ens.fr [this message]
2011-09-04 21:20 ` burnus at gcc dot gnu.org
2011-09-05 12:26 ` janus at gcc dot gnu.org
2011-09-05 12:31 ` burnus at gcc dot gnu.org
2011-09-05 12:50 ` janus at gcc dot gnu.org
2011-09-05 13:52 ` janus at gcc dot gnu.org
2011-09-05 15:20 ` burnus at gcc dot gnu.org
2011-09-05 16:00 ` janus at gcc dot gnu.org
2011-09-05 19:34 ` janus at gcc dot gnu.org
2011-09-05 19:53 ` janus at gcc dot gnu.org
2011-09-06  6:50 ` burnus at gcc dot gnu.org
2011-09-06 12:19 ` janus at gcc dot gnu.org
2011-09-07  8:18 ` burnus at gcc dot gnu.org
2011-09-07 10:58 ` janus at gcc dot gnu.org
2011-09-07 13:33 ` janus at gcc dot gnu.org
2011-09-07 13:45 ` janus 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=bug-50288-4-Fabl5Q7pMy@http.gcc.gnu.org/bugzilla/ \
    --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).