public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Hal Black <hablack@vt.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/7769: using static libraries sometimes loses static initialization Date: Fri, 20 Dec 2002 10:16:00 -0000 [thread overview] Message-ID: <20021220181603.10037.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7769; it has been noted by GNATS. From: Hal Black <hablack@vt.edu> To: Wolfgang Bangerth <bangerth@ticam.utexas.edu> Cc: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c++/7769: using static libraries sometimes loses static initialization Date: Fri, 20 Dec 2002 13:04:55 -0500 Wolfgang Bangerth wrote: > On Thu, 19 Dec 2002, Hal Black wrote: > > >>> 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. >> >>This is a bug. >>[...] >>Correct, the compiler is fine, it is the linker that is not working >>correctly under the circumstances described above. > > > This is just how Unix has worked forever. If you want that changed, file a > report with the binutils people, but I think this is just how it is. Obviously that is the way things should work with C-code - which Unix has been working with forver - since there are no constructors for C functions. However, this is a fallacious argument because C++ is newer than Unix, and doesn't follow C linker rules anyway: C++ needs a C++ linker, not a C linker. Anyway, the binutils seem to do pretty well with other C++ functionality, so I will write them. Thanks for the pointer.
next reply other threads:[~2002-12-20 18:16 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-20 10:16 Hal Black [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-20 8:46 Wolfgang Bangerth 2002-12-19 19:26 Hal Black 2002-12-19 17:40 bangerth 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=20021220181603.10037.qmail@sources.redhat.com \ --to=hablack@vt.edu \ --cc=gcc-prs@gcc.gnu.org \ --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: 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).