public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sfilippone at uniroma2 dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/41656] [OOP] Unresolved GENERIC
Date: Tue, 13 Oct 2009 09:07:00 -0000	[thread overview]
Message-ID: <20091013090700.27691.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41656-9410@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from sfilippone at uniroma2 dot it  2009-10-13 09:06 -------
(In reply to comment #4)
The recent combined patch by Paul makes my compilation progress; however a
little later I get an ICE here: 

#0  0x000000349887efa0 in strcmp () from /lib64/libc.so.6
#1  0x000000000050ffdd in gfc_find_symtree (st=0x128e7d0, name=0x0) at
../../gcc
/gcc/fortran/symbol.c:1810
#2  0x00000000004dd749 in load_derived_extensions () at
../../gcc/gcc/fortran/mo
dule.c:3604
#3  read_module () at ../../gcc/gcc/fortran/module.c:4450
#4  0x00000000004de834 in gfc_use_module () at
../../gcc/gcc/fortran/module.c:36
04
#5  0x00000000004e2ca5 in accept_statement (st=<value optimized out>) at
../../g
cc/gcc/fortran/parse.c:4047
#6  0x00007fffffffd710 in ?? ()
#7  0x00000000004e572e in parse_spec (st=<value optimized out>) at
../../gcc/gcc
/fortran/parse.c:4047
#8  0x00007fffffffd82c in ?? ()
#9  0x0000000000000000 in ?? ()


If this is related to this patch, it needs some more work. Otherwise, I'll cut
the test case and open a new PR


-- 


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


  parent reply	other threads:[~2009-10-13  9:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-10 12:52 [Bug fortran/41656] New: " sfilippone at uniroma2 dot it
2009-10-10 12:53 ` [Bug fortran/41656] " sfilippone at uniroma2 dot it
2009-10-11 16:06 ` pault at gcc dot gnu dot org
2009-10-11 18:19 ` sfilippone at uniroma2 dot it
2009-10-12 13:44 ` sfilippone at uniroma2 dot it
2009-10-13  9:07 ` sfilippone at uniroma2 dot it [this message]
2009-10-16  6:07 ` pault at gcc dot gnu dot org
2009-10-16  6:09 ` pault 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=20091013090700.27691.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: 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).