public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: Petr Ovchenkov <ptr@ParaGraph.Ru> To: Alexandre Oliva <aoliva@redhat.com> Cc: gcc-bugs@gcc.gnu.org Subject: Re: g++ unref symbols Date: Thu, 03 Aug 2000 02:40:00 -0000 [thread overview] Message-ID: <14729.15345.922158.468301@gargle.gargle.HOWL> (raw) In-Reply-To: <or4s52n2u2.fsf@guarana.lsd.ic.unicamp.br> Alexandre Oliva writes: > On Aug 3, 2000, Petr Ovchenkov <ptr@ParaGraph.Ru> wrote: > > > That's was 2.95.2. For later snapshots (mmm, at least since 20000530) > > for A::A scope instead GLOBAL will be LOCAL (on HP) > > I see. AFAIK, WEAK symbols are now supported and used on HP. Maybe > they just show up as `t' symbols? Or maybe it is indeed some new bug? I never see WEAK symbols on HP. c360> uname -a HP-UX c360 B.11.00 A 9000/785 2002760784 two-user license And due to native ld fails link when libraries compiled any gcc after 2.95.2, I think that's 't' isn't designate WEAK (I work with GAS). > > So, summarizing to the list the discussion we've had in private, > given: > > h.h: > struct A { > A() {} > virtual void f(); > }; > > x.cc: > #include "h.h" > void A::f() {} > > y.cc: > #include "h.h" > A a; > > if you compile x.cc and y.cc without optimization, linking fails One another issue should be payed attention: virtual table (and type_info) of A class has local scope, so it still be unresolved on linkage stage. c360> c++ -fPIC -shared -o libA.sl -c lib.cc c360> nm -C libA.sl 00000000 t $CODE$ 40000018 d L$C0000 00000000 t A::A(void) U __rtti_user 00000000 t A type_info function ~~~~~~~~~~~~~~~~~~~~~~ 00000008 C A type_info node 40000000 d A virtual table ~~~~~~~~~~~~~~~~~ 00000000 t gcc2_compiled. 00000000 T A::qq(void) > because the constructor is defined as local in x.o and not defined at > all in y. Is that correct? Yes. That's what I want to say. Thanks. - Petr Ovchenkov
next prev parent reply other threads:[~2000-08-03 2:40 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <14728.14999.948376.245409@gargle.gargle.HOWL> 2000-08-02 16:15 ` Alexandre Oliva [not found] ` <14729.2825.659312.264843@gargle.gargle.HOWL> [not found] ` <orpunqn5pr.fsf@guarana.lsd.ic.unicamp.br> [not found] ` <14729.10392.166467.164794@gargle.gargle.HOWL> [not found] ` <ord7jqn44n.fsf@guarana.lsd.ic.unicamp.br> [not found] ` <14729.12140.47292.22071@gargle.gargle.HOWL> [not found] ` <or4s52n2u2.fsf@guarana.lsd.ic.unicamp.br> 2000-08-03 2:40 ` Petr Ovchenkov [this message] 2000-08-03 7:17 ` Jeffrey A Law
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=14729.15345.922158.468301@gargle.gargle.HOWL \ --to=ptr@paragraph.ru \ --cc=aoliva@redhat.com \ --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).