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/44863] Fortran runtime error: internal error: bad hash value in dynamic dispatch Date: Thu, 08 Jul 2010 07:23:00 -0000 [thread overview] Message-ID: <20100708072252.10094.qmail@sourceware.org> (raw) In-Reply-To: <bug-44863-19196@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from burnus at gcc dot gnu dot org 2010-07-08 07:22 ------- Can you update to GCC 4.6? I get the same error with 4.5, but with 4.6 I get the same result as with NAG or Intel. The reason is that gfortran now uses a proper vtable. Or in the words of http://gcc.gnu.org/gcc-4.6/changes.html : * Improved support for polymorphism between libraries and programs and for complicated inheritance patterns (cf. http://gcc.gnu.org/wiki/OOP) Newer binaries can be found at http://gcc.gnu.org/wiki/GFortranBinaries -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44863
next prev parent reply other threads:[~2010-07-08 7:23 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-08 2:09 [Bug fortran/44863] New: " david dot car7 at gmail dot com 2010-07-08 2:11 ` [Bug fortran/44863] " david dot car7 at gmail dot com 2010-07-08 7:23 ` burnus at gcc dot gnu dot org [this message] 2010-07-10 8:35 ` [Bug fortran/44863] [OOP] " janus at gcc dot gnu dot org 2010-08-21 14:51 ` janus at gcc dot gnu dot org 2010-08-21 15:00 ` 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=20100708072252.10094.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).