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/44869] [OOP] Missing TARGET check - and wrong code or accepts-invalid?
Date: Sun, 11 Jul 2010 08:26:00 -0000 [thread overview]
Message-ID: <20100711082635.7863.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44869-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from janus at gcc dot gnu dot org 2010-07-11 08:26 -------
(In reply to comment #6)
> The runtime segfault persist.
It seems this segfault comes from the call to 'self%assert' in 'test_a'.
The dump shows
self->$vptr->assert->assert_int ((struct class$test_case *) self, &C.1978,
&C.1979, &C.1980, &"generic_tbp.f90"[1]{lb: 1 sz: 1}, &"purposely
failed"[1]{lb: 1 sz: 1}, 15, 16);
which looks ok.
The problem seems to be that the generic TBPs in the vtab are not initialized
properly. The dump contains the correct initialization code for the specific
TBPs, but the init for the generics seems to be missing.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44869
next prev parent reply other threads:[~2010-07-11 8:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 10:28 [Bug fortran/44869] New: " burnus at gcc dot gnu dot org
2010-07-08 10:30 ` [Bug fortran/44869] " burnus at gcc dot gnu dot org
2010-07-08 10:33 ` burnus at gcc dot gnu dot org
2010-07-09 19:02 ` janus at gcc dot gnu dot org
2010-07-09 20:28 ` janus at gcc dot gnu dot org
2010-07-10 9:38 ` janus at gcc dot gnu dot org
2010-07-11 8:09 ` janus at gcc dot gnu dot org
2010-07-11 8:26 ` janus at gcc dot gnu dot org [this message]
2010-07-13 8:44 ` [Bug fortran/44869] [OOP] generic TBPs not initialized properly burnus 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=20100711082635.7863.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).