public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/39996] Double typing of function results not detected Date: Thu, 14 May 2009 09:42:00 -0000 [thread overview] Message-ID: <20090514094212.9500.qmail@sourceware.org> (raw) In-Reply-To: <bug-39996-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from janus at gcc dot gnu dot org 2009-05-14 09:42 ------- Subject: Bug 39996 Author: janus Date: Thu May 14 09:41:41 2009 New Revision: 147528 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=147528 Log: 2009-05-14 Janus Weil <janus@gcc.gnu.org> PR fortran/39996 * decl.c (gfc_match_function_decl): Use gfc_add_type. * symbol.c (gfc_add_type): Better checking for duplicate types in function declarations. And: Always give an error for duplicte types, not just a warning with -std=gnu. 2009-05-14 Janus Weil <janus@gcc.gnu.org> PR fortran/39996 * gfortran.dg/func_decl_2.f90: Modified (replacing warnings by errors). * gfortran.dg/duplicate_type_2.f90: Ditto. * gfortran.dg/duplicate_type_3.f90: New. Added: trunk/gcc/testsuite/gfortran.dg/duplicate_type_3.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/decl.c trunk/gcc/fortran/symbol.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gfortran.dg/duplicate_type_2.f90 trunk/gcc/testsuite/gfortran.dg/func_decl_2.f90 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39996
next prev parent reply other threads:[~2009-05-14 9:42 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-05-01 19:26 [Bug fortran/39996] New: " burnus at gcc dot gnu dot org 2009-05-05 20:35 ` [Bug fortran/39996] " janus at gcc dot gnu dot org 2009-05-09 20:53 ` janus at gcc dot gnu dot org 2009-05-14 9:42 ` janus at gcc dot gnu dot org [this message] 2009-05-14 9:46 ` janus 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=20090514094212.9500.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).