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/61527] [4.9/5 Regression] class/extends, multiple generic assignment, accept invalid
Date: Fri, 16 Jan 2015 17:16:00 -0000 [thread overview]
Message-ID: <bug-61527-4-Y63QRvvrHs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61527-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61527
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |janus at gcc dot gnu.org
--- Comment #6 from janus at gcc dot gnu.org ---
(In reply to Tobias Burnus from comment #3)
> It seems to be due to the following code in interface.c, which was added for
> PR57530 in r201329:
Reverting this part of the patch ...
Index: gcc/fortran/interface.c
===================================================================
--- gcc/fortran/interface.c (Revision 219753)
+++ gcc/fortran/interface.c (Arbeitskopie)
@@ -515,12 +515,6 @@
if (s2->attr.ext_attr & (1 << EXT_ATTR_NO_ARG_CHECK))
return 1;
- /* TYPE and CLASS of the same declared type are type compatible,
- but have different characteristics. */
- if ((s1->ts.type == BT_CLASS && s2->ts.type == BT_DERIVED)
- || (s1->ts.type == BT_DERIVED && s2->ts.type == BT_CLASS))
- return 0;
-
return gfc_compare_types (&s1->ts, &s2->ts) || s2->ts.type == BT_ASSUMED;
}
... indeed brings back the expected error message for comment 0. However, it
causes a few testsuite regressions:
FAIL: gfortran.dg/dummy_procedure_4.f90 -O (test for errors, line 28)
FAIL: gfortran.dg/proc_ptr_30.f90 -O (test for errors, line 25)
FAIL: gfortran.dg/proc_ptr_comp_32.f90 -O (test for errors, line 34)
FAIL: gfortran.dg/proc_ptr_comp_33.f90 -O (test for errors, line 14)
FAIL: gfortran.dg/proc_ptr_comp_33.f90 -O (test for errors, line 54)
next prev parent reply other threads:[~2015-01-16 17:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 16:06 [Bug fortran/61527] New: " mrestelli at gmail dot com
2014-06-16 16:19 ` [Bug fortran/61527] " dominiq at lps dot ens.fr
2014-06-16 16:38 ` mrestelli at gmail dot com
2014-07-12 21:33 ` [Bug fortran/61527] [4.9/4.10 Regression] " burnus at gcc dot gnu.org
2014-07-12 22:05 ` dominiq at lps dot ens.fr
2014-10-30 10:40 ` [Bug fortran/61527] [4.9/5 " jakub at gcc dot gnu.org
2014-11-24 16:45 ` rguenth at gcc dot gnu.org
2015-01-16 17:16 ` janus at gcc dot gnu.org [this message]
2015-01-16 17:43 ` janus at gcc dot gnu.org
2015-06-26 20:01 ` [Bug fortran/61527] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:31 ` jakub at gcc dot gnu.org
2021-05-14 9:47 ` [Bug fortran/61527] [9/10/11/12 Regression] [OOP] " jakub at gcc dot gnu.org
2021-06-01 8:06 ` rguenth at gcc dot gnu.org
2022-05-27 9:35 ` [Bug fortran/61527] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:30 ` jakub at gcc dot gnu.org
2023-07-07 10:30 ` [Bug fortran/61527] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-04-26 10:06 ` pault 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-61527-4-Y63QRvvrHs@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).