From: George Danchev <danchev@spnet.net>
To: Ian Lance Taylor <iant@google.com>
Cc: f.b.brokken@rug.nl, gcc-help@gcc.gnu.org,
tony mancill <tmancill@debian.org>
Subject: Re: missing symbols with bobcat C++ library on armel
Date: Fri, 27 May 2011 08:13:00 -0000 [thread overview]
Message-ID: <201105261952.18362.danchev@spnet.net> (raw)
In-Reply-To: <mcr8vtudehj.fsf@coign.corp.google.com>
On Wednesday 25 May 2011 17:47:04 Ian Lance Taylor wrote:
Hi,
> > Since it looks like armel's compiler skips the inline definitions of
> > virtual members when compiling for a shared library, we're in the
> > process of removing all inline definitions of virtual members, replacing
> > them by non-inline definitions in separate source files. From tests done
> > so far by George Danchev we get the impression that this might very well
> > solve (or bypass?) the issue.
>
> Yes, that should work.
Dropping inline from virtual methods worked indeed:
build daemons logs:
https://buildd.debian.org/status/fetch.php?pkg=bobcat&arch=armel&ver=2.16.00-1&stamp=1306411374
https://buildd.debian.org/status/fetch.php?pkg=stealth&arch=armel&ver=2.01.00-3&stamp=1306426051
However, it is still unclear why the compiler would behave differently on
armel, and not simply ignoring the inline request as it does on other
architectures. This is a subtle behavior and smells like a bug in the compiler
itself. Should we prepare a sample code manifesting the issue and file a bug
against gcc?
Thanks for the help so far.
--
pub 4096R/0E4BD0AB <people.fccf.net/danchev/key pgp.mit.edu>
next prev parent reply other threads:[~2011-05-26 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 8:30 George Danchev
2011-05-25 13:48 ` Ian Lance Taylor
2011-05-25 15:14 ` Frank B. Brokken
2011-05-25 16:13 ` Ian Lance Taylor
2011-05-25 18:22 ` Frank B. Brokken
2011-05-25 18:43 ` Ian Lance Taylor
2011-05-25 19:10 ` Axel Freyn
2011-05-25 22:33 ` Frank B. Brokken
2011-05-27 8:13 ` George Danchev [this message]
2011-05-27 13:39 ` Ian Lance Taylor
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=201105261952.18362.danchev@spnet.net \
--to=danchev@spnet.net \
--cc=f.b.brokken@rug.nl \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.com \
--cc=tmancill@debian.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).