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/46244] New: gfc_compare_derived_types is buggy
Date: Sat, 30 Oct 2010 14:24:00 -0000 [thread overview]
Message-ID: <bug-46244-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46244
Summary: gfc_compare_derived_types is buggy
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: janus@gcc.gnu.org
As noted by Dominique in PR 46196 comment #5, there is a problem in
gfc_compare_derived_types (interface.c):
--- ../_clean/gcc/fortran/interface.c 2010-10-27 23:47:20.000000000 +0200
+++ gcc/fortran/interface.c 2010-10-29 10:55:07.000000000 +0200
@@ -445,16 +445,16 @@ gfc_compare_derived_types (gfc_symbol *d
/* Make sure that link lists do not put this function into an
endless recursive loop! */
if (!(dt1->ts.type == BT_DERIVED && derived1 == dt1->ts.u.derived)
- && !(dt1->ts.type == BT_DERIVED && derived1 == dt1->ts.u.derived)
+ && !(dt2->ts.type == BT_DERIVED && derived2 == dt2->ts.u.derived)
&& gfc_compare_types (&dt1->ts, &dt2->ts) == 0)
return 0;
else if ((dt1->ts.type == BT_DERIVED && derived1 == dt1->ts.u.derived)
- && !(dt1->ts.type == BT_DERIVED && derived1 == dt1->ts.u.derived))
+ && !(dt2->ts.type == BT_DERIVED && derived2 == dt2->ts.u.derived))
return 0;
else if (!(dt1->ts.type == BT_DERIVED && derived1 == dt1->ts.u.derived)
- && (dt1->ts.type == BT_DERIVED && derived1 == dt1->ts.u.derived))
+ && (dt2->ts.type == BT_DERIVED && derived2 == dt2->ts.u.derived))
return 0;
dt1 = dt1->next;
next reply other threads:[~2010-10-30 14:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 14:24 janus at gcc dot gnu.org [this message]
2010-10-30 14:30 ` [Bug fortran/46244] " janus at gcc dot gnu.org
2010-10-30 14:54 ` janus at gcc dot gnu.org
2010-10-30 15:04 ` janus at gcc dot gnu.org
2010-10-30 15:11 ` janus at gcc dot gnu.org
2010-10-30 16:02 ` mikael at gcc dot gnu.org
2010-10-30 16:04 ` mikael at gcc dot gnu.org
2010-11-05 13:56 ` dominiq at lps dot ens.fr
2010-11-05 15:01 ` burnus at gcc dot gnu.org
2010-11-06 13:00 ` burnus at gcc dot gnu.org
2010-11-10 17:45 ` burnus at gcc dot gnu.org
2010-11-10 17:49 ` burnus at gcc dot gnu.org
2011-02-20 16:58 ` mikael at gcc dot gnu.org
2011-02-20 17:01 ` mikael at gcc dot gnu.org
2011-02-20 21:07 ` dominiq at lps dot ens.fr
2011-02-20 22:20 ` dominiq at lps dot ens.fr
2011-02-20 23:18 ` mikael at gcc dot gnu.org
2011-02-21 9:37 ` paul.richard.thomas at gmail dot com
2011-10-02 17:47 ` dominiq at lps dot ens.fr
2011-10-02 22:06 ` mikael at gcc dot gnu.org
2024-01-19 18:00 ` mikael 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-46244-4@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).