public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/50288] FAIL: gfortran.dg/class_45b.f03
Date: Mon, 05 Sep 2011 19:53:00 -0000 [thread overview]
Message-ID: <bug-50288-4-Rht88H4LQt@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 #13 from janus at gcc dot gnu.org 2011-09-05 19:52:53 UTC ---
Ok, since class_45{a,b} is not really a run-time test, I think the best
solution would be to just convert it to "dg-do link":
Index: class_45b.f03
===================================================================
--- class_45b.f03 (revision 178551)
+++ class_45b.f03 (working copy)
@@ -1,4 +1,4 @@
-! { dg-do run }
+! { dg-do link }
! { dg-additional-sources class_45a.f03 }
!
! PR 50227: [4.7 Regression] [OOP] ICE-on-valid with allocatable class
variable
I assume this should get rid of the errors. Can anyone confirm that? (Since I
do not see the failures, I can not check it myself.)
One could do the same with class_4{a,b,c}, since this one also does not contain
any actual run-time checking (but was committed to check for a compile-time
error).
If I get a confirmation the the above patch fixes the errors, I will commit it
as obvious.
next prev parent reply other threads:[~2011-09-05 19:53 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
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 [this message]
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-Rht88H4LQt@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).