public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, hablack@vt.edu,
	nobody@gcc.gnu.org
Subject: Re: c++/7769: using static libraries sometimes loses static initialization
Date: Thu, 19 Dec 2002 17:40:00 -0000	[thread overview]
Message-ID: <20021220014005.15538.qmail@sources.redhat.com> (raw)

Synopsis: using static libraries sometimes loses static initialization

State-Changed-From-To: open->closed
State-Changed-By: bangerth
State-Changed-When: Thu Dec 19 17:40:05 2002
State-Changed-Why:
    This is not a bug. When you want that a particular 
    object file (possibly within an archive) is pulled into you
    executable for sure, then you have to reference an object
    inside it.
    
    If you rename your class "A" to "ComplexClass", to make
    its symbols better visible in the executable, you
    see that the object file with the static constructor
    is not even pulled into the executable:
    g/static_init> nm main1 | grep ComplexClass
    080485f0 W __12ComplexClass
    g/static_init> nm main2 | grep ComplexClass
    g/static_init> nm main3 | grep ComplexClass
    g/static_init> nm main4 | grep ComplexClass
    080485f0 W __12ComplexClass
    
    I guess this is just how the linker works.
    
    W.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7769


             reply	other threads:[~2002-12-20  1:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19 17:40 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-20 10:16 Hal Black
2002-12-20  8:46 Wolfgang Bangerth
2002-12-19 19:26 Hal Black
2002-09-12 18:06 Hal Black
2002-08-29 20:16 hablack

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=20021220014005.15538.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=hablack@vt.edu \
    --cc=nobody@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).