public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/42207] [OOP] Compile-time errors on typed allocation and pointer function result assignment Date: Tue, 03 Aug 2010 10:03:00 -0000 [thread overview] Message-ID: <20100803100334.8762.qmail@sourceware.org> (raw) In-Reply-To: <bug-42207-15301@http.gcc.gnu.org/bugzilla/> ------- Comment #8 from burnus at gcc dot gnu dot org 2010-08-03 10:03 ------- If I run the code in comment 4 with an appended "end" (to make it a complete program), I (still) get link errors: /tmp/cc3J3Ygi.o: In function `__m_MOD_new_bar': aa3.f90:(.text+0x2c): undefined reference to `vtab$bar.1527' That's with trunk 4.6.0 20100803 (Rev. 162828) x86_64-unknown-linux-gnu with both -m32 and -m64 - thus I do not think that this is target dependent. The problem is also obvious: No vtable is created - as mentioned the other day, I think generating the vtable only when using the a polymorphic type - but then initializing it several times - seems to be the wrong approach. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42207
next prev parent reply other threads:[~2010-08-03 10:03 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-11-28 18:14 [Bug fortran/42207] New: " damian at rouson dot net 2009-11-28 18:25 ` [Bug fortran/42207] " sfilippone at uniroma2 dot it 2009-11-28 20:18 ` dominiq at lps dot ens dot fr 2009-11-29 2:50 ` damian at rouson dot net 2009-11-29 12:31 ` [Bug fortran/42207] [OOP] " janus at gcc dot gnu dot org 2009-11-29 16:22 ` dominiq at lps dot ens dot fr 2009-11-30 0:52 ` damian at rouson dot net 2009-11-30 1:16 ` damian at rouson dot net 2010-08-03 10:03 ` burnus at gcc dot gnu dot org [this message] 2010-08-03 11:36 ` janus at gcc dot gnu dot org 2010-08-03 11:49 ` dominiq at lps dot ens dot fr 2010-08-03 11:51 ` burnus at gcc dot gnu dot org 2010-08-03 12:59 ` janus at gcc dot gnu dot org 2010-08-03 13:43 ` dominiq at lps dot ens dot fr 2010-08-03 14:31 ` mikael at gcc dot gnu dot org 2010-08-03 15:31 ` dominiq at lps dot ens dot fr 2010-08-03 16:32 ` janus at gcc dot gnu dot org 2010-08-03 18:08 ` dominiq at lps dot ens dot fr 2010-08-03 18:55 ` dominiq at lps dot ens dot fr 2010-08-04 7:31 ` janus at gcc dot gnu dot org 2010-08-04 19:49 ` janus at gcc dot gnu dot org 2010-08-04 20:01 ` janus 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=20100803100334.8762.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).