public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/44065] [OOP] Undefined reference to vtab$...
Date: Wed, 04 Aug 2010 22:59:00 -0000 [thread overview]
Message-ID: <20100804225856.17325.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44065-18960@http.gcc.gnu.org/bugzilla/>
------- Comment #13 from dominiq at lps dot ens dot fr 2010-08-04 22:58 -------
> r162879 seems to fix all the test cases for me. Can anyone confirm that comment
> #0 works now without any linking errors?
On x86_64-apple-darwin10.4.0 at r162881, I have tested all the codelets I have
for the PRs fixed by r162879 with both -m32 and -m64 without linking error.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44065
next prev parent reply other threads:[~2010-08-04 22:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 17:17 [Bug libfortran/44065] New: Undefined reference to TBP pchwood at yahoo dot com
2010-05-10 17:32 ` [Bug libfortran/44065] " dominiq at lps dot ens dot fr
2010-05-10 22:06 ` [Bug fortran/44065] [OOP] " janus at gcc dot gnu dot org
2010-06-06 3:38 ` [Bug fortran/44065] [OOP] Undefined reference to vtab$ janus at gcc dot gnu dot org
2010-07-17 8:49 ` janus at gcc dot gnu dot org
2010-08-03 16:37 ` janus at gcc dot gnu dot org
2010-08-03 16:44 ` janus at gcc dot gnu dot org
2010-08-03 16:54 ` janus at gcc dot gnu dot org
2010-08-03 17:01 ` dominiq at lps dot ens dot fr
2010-08-03 18:57 ` dominiq at lps dot ens dot fr
2010-08-04 8:32 ` janus at gcc dot gnu dot org
2010-08-04 19:49 ` janus at gcc dot gnu dot org
2010-08-04 20:05 ` janus at gcc dot gnu dot org
2010-08-04 22:59 ` dominiq at lps dot ens dot fr [this message]
2010-08-05 11:58 ` 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=20100804225856.17325.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).