public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/52887] Bootstrap on AIX failure: Undefined symbol: .std::function<void (std::__regex::_PatternCursor const&, std::__regex::_Results&)>::function(std::function<void (std::__regex::_PatternCursor const&, std::__regex::_Results&)> const&)
Date: Wed, 20 Jun 2012 13:25:00 -0000	[thread overview]
Message-ID: <bug-52887-4-3P5C7qY8em@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52887-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52887

--- Comment #17 from David Edelsohn <dje at gcc dot gnu.org> 2012-06-20 13:25:31 UTC ---
Another feature of AIX is its garbage-collecting linker. The very first
implementation of GCC for AIX was forced to emit an extra symbol to tie the
text section to the data section to prevent the linker from garbage collecting
a related section that did not have an obvious reference. This introduces an
extra dependency and may pull in unreferenced data sections from object files.
libstdc++ is built with --function-sections and --data-sections, which should
minimize this, but, again, if an application is relying upon the linker to
ignore missing definitions of symbols, it may behave differently on AIX.


  parent reply	other threads:[~2012-06-20 13:25 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06 15:38 [Bug bootstrap/52887] New: " skunk at iskunk dot org
2012-04-10  9:13 ` [Bug bootstrap/52887] " redi at gcc dot gnu.org
2012-05-10 14:39 ` skunk at iskunk dot org
2012-05-10 15:04 ` redi at gcc dot gnu.org
2012-05-10 15:52 ` skunk at iskunk dot org
2012-05-10 22:14 ` skunk at iskunk dot org
2012-05-11 17:09 ` skunk at iskunk dot org
2012-05-11 18:39 ` redi at gcc dot gnu.org
2012-05-12  5:37 ` skunk at iskunk dot org
2012-05-12  9:15 ` paolo.carlini at oracle dot com
2012-06-18  9:44 ` joerg.richter@pdv-fs.de
2012-06-18 15:26 ` redi at gcc dot gnu.org
2012-06-18 16:57 ` skunk at iskunk dot org
2012-06-19 23:21 ` dje at gcc dot gnu.org
2012-06-20  1:36 ` redi at gcc dot gnu.org
2012-06-20  4:11 ` skunk at iskunk dot org
2012-06-20  8:50 ` redi at gcc dot gnu.org
2012-06-20 13:25 ` dje at gcc dot gnu.org [this message]
2012-06-20 21:15 ` dje at gcc dot gnu.org
2012-06-21  6:58 ` joerg.richter@pdv-fs.de
2012-06-21  8:24 ` redi at gcc dot gnu.org
2012-07-25  3:19 ` skunk at iskunk dot org
2012-09-14  7:58 ` joerg.richter@pdv-fs.de
2012-09-16  2:37 ` dje at gcc dot gnu.org
2012-11-21  8:03 ` gilles.pion at gmail dot com
2012-11-26  2:50 ` dje at gcc dot gnu.org
2013-01-17  1:40 ` redi at gcc dot gnu.org
2013-01-17  1:41 ` redi at gcc dot gnu.org
2013-02-11 23:54 ` bkoz at gcc dot gnu.org

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=bug-52887-4-3P5C7qY8em@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --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: 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).