public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/55854] ICE on intent(out) dummy argument with unlimited polymorphic component
Date: Thu, 03 Jan 2013 13:04:00 -0000	[thread overview]
Message-ID: <bug-55854-4-ISpyG37nPd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55854-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55854

--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> 2013-01-03 13:03:49 UTC ---
(In reply to comment #1)
> I think it's the same as PR55763 comment 10.

Seemingly not - at least with the patch from PR55763 comment 12, this example
crashes in:

#0  build_function_decl (sym=0x1658420, global=<optimized out>) at
../../gcc/fortran/trans-decl.c:1852
#1  0x0000000000613e37 in gfc_get_symbol_decl (sym=0x1658420) at
../../gcc/fortran/trans-decl.c:1370


The following assert fails for sym == "__copy_CLASS_0_":

1848      /* Allow only one nesting level.  Allow public declarations.  */
1849      gcc_assert (current_function_decl == NULL_TREE
1850                  || DECL_FILE_SCOPE_P (current_function_decl)
1851                  || (TREE_CODE (DECL_CONTEXT (current_function_decl))
1852                      == NAMESPACE_DECL));

Here, "current_function_decl" is "function_decl bar.


  parent reply	other threads:[~2013-01-03 13:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03  3:00 [Bug fortran/55854] New: " damian at rouson dot net
2013-01-03  9:41 ` [Bug fortran/55854] " burnus at gcc dot gnu.org
2013-01-03 13:04 ` burnus at gcc dot gnu.org [this message]
2013-01-03 14:47 ` burnus at gcc dot gnu.org
2013-01-03 18:12 ` damian at rouson dot net
2013-01-03 18:55 ` burnus at gcc dot gnu.org
2013-01-03 19:12 ` damian at rouson dot net
2013-01-04  8:58 ` burnus at gcc dot gnu.org
2013-01-04  9:01 ` burnus 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-55854-4-ISpyG37nPd@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).