public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikael at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/42051] [OOP] ICE on array-valued function with CLASS formal argument Date: Mon, 02 Aug 2010 15:31:00 -0000 [thread overview] Message-ID: <20100802153108.7543.qmail@sourceware.org> (raw) In-Reply-To: <bug-42051-15301@http.gcc.gnu.org/bugzilla/> ------- Comment #21 from mikael at gcc dot gnu dot org 2010-08-02 15:31 ------- Subject: Bug 42051 Author: mikael Date: Mon Aug 2 15:30:47 2010 New Revision: 162821 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=162821 Log: 2010-08-02 Mikael Morin <mikael@gcc.gnu.org> Janus Weil <janus@gcc.gnu.org> PR fortran/42051 PR fortran/44064 PR fortran/45151 * intrinsic.c (gfc_get_intrinsic_sub_symbol): Commit changed symbol. * symbol.c (gen_cptr_param, gen_fptr_param, gen_shape_param, gfc_copy_formal_args, gfc_copy_formal_args_intr, gfc_copy_formal_args_ppc, generate_isocbinding_symbol): Ditto. * parse.c (parse_derived_contains, parse_spec, parse_progunit): Call reject_statement in case of error. (match_deferred_characteritics): Call gfc_undo_symbols in case match fails. Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/intrinsic.c trunk/gcc/fortran/parse.c trunk/gcc/fortran/symbol.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42051
next prev parent reply other threads:[~2010-08-02 15:31 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-11-15 16:25 [Bug fortran/42051] New: ICE on allocatable array TBP result damian at rouson dot net 2009-11-15 18:31 ` [Bug fortran/42051] " janus at gcc dot gnu dot org 2009-11-15 18:50 ` [Bug fortran/42051] [OOP] ICE on array-valued function with CLASS formal argument janus at gcc dot gnu dot org 2009-12-03 21:28 ` pault at gcc dot gnu dot org 2009-12-03 21:46 ` pault at gcc dot gnu dot org 2009-12-04 13:18 ` dominiq at lps dot ens dot fr 2010-03-02 23:31 ` janus at gcc dot gnu dot org 2010-06-11 2:50 ` janus at gcc dot gnu dot org 2010-06-11 2:56 ` janus at gcc dot gnu dot org 2010-06-11 16:46 ` janus at gcc dot gnu dot org 2010-06-15 19:08 ` janus at gcc dot gnu dot org 2010-06-15 19:38 ` janus at gcc dot gnu dot org 2010-06-15 19:41 ` janus at gcc dot gnu dot org 2010-06-27 13:14 ` mikael at gcc dot gnu dot org 2010-06-27 13:16 ` mikael at gcc dot gnu dot org 2010-06-27 14:39 ` paul dot richard dot thomas at gmail dot com 2010-07-15 21:37 ` dfranke at gcc dot gnu dot org 2010-07-28 20:01 ` mikael at gcc dot gnu dot org 2010-07-29 11:23 ` mikael at gcc dot gnu dot org 2010-07-29 11:53 ` mikael at gcc dot gnu dot org 2010-07-31 10:28 ` mikael at gcc dot gnu dot org 2010-08-02 15:31 ` mikael at gcc dot gnu dot org [this message] 2010-08-04 14:18 ` mikael at gcc dot gnu dot org 2010-08-05 12:12 ` janus at gcc dot gnu dot org 2010-08-05 12:59 ` mikael at gcc dot gnu dot org 2010-08-05 21:09 ` mikael at gcc dot gnu dot org 2010-08-05 21:11 ` mikael at gcc dot gnu dot org [not found] <bug-42051-4@http.gcc.gnu.org/bugzilla/> 2011-08-16 21:23 ` 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=20100802153108.7543.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).