public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dannysmith at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/37660] [4.4 Regression] Error Building libssp, recent update
Date: Fri, 16 Jan 2009 07:14:00 -0000 [thread overview]
Message-ID: <20090116071438.5128.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37660-6183@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from dannysmith at users dot sourceforge dot net 2009-01-16 07:14 -------
(In reply to comment #4)
> I've just run into this problem too.
> In earlier versions of Aaron's shared libgcc patch, we extracted ctors.o and
> chkstk.o and placed them whole into the import lib. I'm not sure why he didn't
> do this in the committed version, but it has the effect that you have to link
> against the static libgcc as well as the shared one in order to let it fill out
> any missing references. I'm not sure I'm entirely comfortable with that,
> although I can't think of any obvious problem, but it seems wrong to link
> against such a duplicated body of code to me, and I think I'd prefer the import
> lib solution for cygwin's compiler.
If you look at the (static) libgcc.a, when shared libs are enabled, it
contains only symbols that are not exported from the shared dll. Only the
'API-stable' symbols are exported. That is a good thing. So the libgcc.a code
does not duplicate any code in libgcc_s.[a|dll].
--
dannysmith at users dot sourceforge dot net changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2009-01-16 07:14:38
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37660
next prev parent reply other threads:[~2009-01-16 7:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-27 16:37 [Bug bootstrap/37660] New: " mckelvey at maskull dot com
2008-11-29 19:00 ` [Bug bootstrap/37660] " mckelvey at maskull dot com
2009-01-14 15:20 ` piotr dot wyderski at gmail dot com
2009-01-15 1:10 ` [Bug bootstrap/37660] [4.4 Regression] " pinskia at gcc dot gnu dot org
2009-01-15 2:39 ` dannysmith at users dot sourceforge dot net
2009-01-15 15:54 ` rguenth at gcc dot gnu dot org
2009-01-15 19:08 ` dave dot korn dot cygwin at gmail dot com
2009-01-16 7:14 ` dannysmith at users dot sourceforge dot net [this message]
2009-01-16 13:41 ` dave dot korn dot cygwin at gmail dot com
2009-01-18 5:57 ` dave dot korn dot cygwin at gmail dot com
2009-01-19 4:22 ` dannysmith at users dot sourceforge dot net
2009-01-19 4:54 ` dave dot korn dot cygwin at gmail dot com
2009-01-19 22:29 ` mckelvey at maskull dot com
2009-01-20 4:33 ` dave dot korn dot cygwin at gmail dot com
2009-01-21 19:20 ` davek at gcc dot gnu dot org
2009-01-24 8:23 ` billingd at gcc dot gnu dot org
2009-01-24 16:56 ` jakub at gcc dot gnu dot org
2009-01-24 18:21 ` dave dot korn dot cygwin at gmail dot com
2009-01-24 23:14 ` billingd at gcc dot gnu dot org
2009-01-24 23:15 ` dave dot korn dot cygwin at gmail dot com
2009-01-24 23:22 ` dave dot korn dot cygwin at gmail dot com
2009-01-25 1:22 ` mckelvey at maskull dot com
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=20090116071438.5128.qmail@sourceware.org \
--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).