public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: Uwe Kindler <uwe.kindler@cetoni.de>, ecos-patches@sourceware.org
Subject: Re: eCos uSTL 1.3 port for review
Date: Fri, 07 Aug 2009 12:06:00 -0000	[thread overview]
Message-ID: <20090807120706.GA2335@sg-ubuntu.local> (raw)
In-Reply-To: <4A7C11A7.6000306@dallaway.org.uk>

John Dallaway wrote:
> Hi Uwe
> 
> Uwe Kindler wrote:
> 
> > thank you for your investigation and for your detailed error report.
> > Does someone of the eCos folks know a better way to solve the
> > __cxa_pure_virtual issue or should we go with Sergei's proposal
> > 
> > -Wl,--defsym -Wl,__cxa_pure_virtual=0
> 
> CYGPKG_INFRA is supposed to provide a replacement implementation of this
> function. Did you try adding your own implementation of
> __cxxabiv1::__cxa_pure_virtual() as discussed on the ecos-devel list?

Hi Jonh,

Are such implementations (in pure.cxx) useful? I'm looking on linker
group

    GROUP(libtarget.a libgcc.a libsupc++.a)

    $ nm install/lib/libtarget.a | grep __cxa_pure_virtual
    00000000 T __cxa_pure_virtual

Okay it came there from infra_pure.o. Is it right? But, there is next
implementation in libsupc++.a.

    $ nm i386-elf/i386-elf/lib/libsupc++.a 2>/dev/null | grep __cxa_pure_virtual
             U __cxa_pure_virtual
    00000000 T __cxa_pure_virtual

I think arm-eabi chain is the same.

RFC: What kind of implementation will be used then? Well, using 'ar x' I
would answer :-) but may be you just know.

Thanks for any clarifications,

Sergei

  reply	other threads:[~2009-08-07 12:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06  8:31 cetoni GmbH - Uwe Kindler
2009-08-06 12:19 ` Sergei Gavrikov
2009-08-06 12:30   ` cetoni GmbH - Uwe Kindler
2009-08-06 12:43     ` Sergei Gavrikov
2009-08-06 13:24       ` Sergei Gavrikov
2009-08-06 13:55         ` Sergei Gavrikov
2009-08-07 11:31           ` Sergei Gavrikov
2009-08-07 13:52             ` Jonathan Larmour
2009-08-07 16:01               ` Sergei Gavrikov
2009-08-07 16:15                 ` Sergei Gavrikov
2009-08-07 19:21                   ` Jonathan Larmour
     [not found]         ` <4A7ADFF5.2000009@cetoni.de>
     [not found]           ` <20090806140807.GA26049@sg-ubuntu.local>
2009-08-07  5:54             ` cetoni GmbH - Uwe Kindler
2009-08-07  7:13               ` Sergei Gavrikov
2009-08-07  9:40                 ` Sergei Gavrikov
2009-08-07 11:18                   ` cetoni GmbH - Uwe Kindler
2009-08-07 11:36                     ` John Dallaway
2009-08-07 12:06                       ` Sergei Gavrikov [this message]
2009-08-07 13:13                         ` Jonathan Larmour

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=20090807120706.GA2335@sg-ubuntu.local \
    --to=sergei.gavrikov@gmail.com \
    --cc=ecos-patches@sourceware.org \
    --cc=john@dallaway.org.uk \
    --cc=uwe.kindler@cetoni.de \
    /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).