public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/47085] [OOP] Problem in allocate( SOURCE=) for polymorphic component Date: Wed, 29 Dec 2010 22:44:00 -0000 [thread overview] Message-ID: <bug-47085-4-vwhPdzsCx9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47085-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47085 --- Comment #2 from janus at gcc dot gnu.org 2010-12-29 22:44:26 UTC --- While reducing the test case I noticed that the following invalid code triggers an ICE: type :: t0 end type class(t0) :: x allocate(x) end Backtrace: Program received signal SIGSEGV, Segmentation fault. 0x0000000000520e06 in gfc_match_varspec (primary=0x1939130, equiv_flag=0, sub_flag=0 '\000', ppc_arg=0 '\000') at /home/jweil/gcc46/trunk/gcc/fortran/primary.c:1777 1777 || (sym->ts.type == BT_CLASS && CLASS_DATA (sym)->attr.dimension)) (gdb) bt #0 0x0000000000520e06 in gfc_match_varspec (primary=0x1939130, equiv_flag=0, sub_flag=0 '\000', ppc_arg=0 '\000') at /home/jweil/gcc46/trunk/gcc/fortran/primary.c:1777 #1 0x0000000000523b56 in match_variable (result=0x192eb80, equiv_flag=0, host_flag=1) at /home/jweil/gcc46/trunk/gcc/fortran/primary.c:3104 #2 0x0000000000523bac in gfc_match_variable (result=0x192eb80, equiv_flag=0) at /home/jweil/gcc46/trunk/gcc/fortran/primary.c:3119 #3 0x0000000000503697 in gfc_match_allocate () at /home/jweil/gcc46/trunk/gcc/fortran/match.c:2908
next prev parent reply other threads:[~2010-12-29 22:44 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-28 20:40 [Bug fortran/47085] New: " sfilippone at uniroma2 dot it 2010-12-29 22:39 ` [Bug fortran/47085] " janus at gcc dot gnu.org 2010-12-29 22:44 ` janus at gcc dot gnu.org [this message] 2010-12-30 11:53 ` janus at gcc dot gnu.org 2011-01-02 17:52 ` 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=bug-47085-4-vwhPdzsCx9@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: 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).