public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/30239] duplicate data type assignment not detected Date: Sun, 17 Dec 2006 20:16:00 -0000 [thread overview] Message-ID: <20061217201556.5130.qmail@sourceware.org> (raw) In-Reply-To: <bug-30239-13648@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from burnus at gcc dot gnu dot org 2006-12-17 20:15 ------- This is because in symbol.c's gfc_add_type there is const char *msg = "Symbol '%s' at %L already has basic type of %s"; if (!(sym->ts.type == ts->typesym->ts.type == ts->type && (sym->attr.flavor == FL_PROCEDURE || sym->attr.result)) || gfc_notification_std (GFC_STD_GNU) == ERROR || pedantic) { gfc_error (msg, sym->name, where, gfc_basic_typename (sym->ts.type)); return FAILURE; } The !(sym->ts.type == ts->type) prevents the error message. Removing this check should all what is needed for this bug. But this might break other cases were it is allowed. (I didn't check/though about those, however). -- burnus at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu dot | |org Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2006-12-17 20:15:55 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30239
next prev parent reply other threads:[~2006-12-17 20:16 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-12-17 16:48 [Bug fortran/30239] New: " dfranke at gcc dot gnu dot org 2006-12-17 20:16 ` burnus at gcc dot gnu dot org [this message] 2006-12-18 6:02 ` [Bug fortran/30239] " pault at gcc dot gnu dot org 2006-12-18 7:49 ` burnus at gcc dot gnu dot org 2006-12-18 8:20 ` dfranke at gcc dot gnu dot org 2008-08-22 7:19 ` domob at gcc dot gnu dot org 2008-08-22 11:41 ` domob at gcc dot gnu dot org 2008-08-22 12:48 ` dfranke at gcc dot gnu dot org 2008-08-22 20:38 ` domob at gcc dot gnu dot org 2008-08-22 20:39 ` domob at gcc dot gnu dot 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=20061217201556.5130.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: linkBe 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).