public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "developer at sandoe-acoustics dot co dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/39888] TLS emutls not linked to automatically on Darwin
Date: Thu, 24 Sep 2009 07:47:00 -0000 [thread overview]
Message-ID: <20090924074647.31278.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39888-4688@http.gcc.gnu.org/bugzilla/>
------- Comment #26 from developer at sandoe-acoustics dot co dot uk 2009-09-24 07:46 -------
(In reply to comment #24)
> I am confused why libgcc_ext needs to be built as 10.4/10.5 versions. Aren't
the _ext is versioned - precisely because the symbols included in the OS
version changes between OS revisions. No only that, but there are different
symbol sets between 32 and 64 bit libs.
As far as darwin8 and darwin9 are concerned - I have no better offer than the
_ext as formulated above (I will try and update the patches in the next couple
of weeks).
As far as darwin10 is concerned Mike's solution needs implementation and
evaluation, if we are to adopt it. I'll try and find a free machine to put
darwin10 on.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39888
next prev parent reply other threads:[~2009-09-24 7:47 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 18:39 [Bug other/39888] New: " fago at earthlink dot net
2009-04-27 19:04 ` [Bug other/39888] " developer at sandoe-acoustics dot co dot uk
2009-04-27 19:05 ` developer at sandoe-acoustics dot co dot uk
2009-04-27 19:06 ` developer at sandoe-acoustics dot co dot uk
2009-04-27 19:07 ` developer at sandoe-acoustics dot co dot uk
2009-04-27 19:15 ` developer at sandoe-acoustics dot co dot uk
2009-09-22 18:56 ` mrs at apple dot com
2009-09-22 19:20 ` developer at sandoe-acoustics dot co dot uk
2009-09-22 21:18 ` mrs at apple dot com
2009-09-23 3:02 ` howarth at nitro dot med dot uc dot edu
2009-09-23 15:50 ` howarth at nitro dot med dot uc dot edu
2009-09-23 16:00 ` developer at sandoe-acoustics dot co dot uk
2009-09-23 16:19 ` howarth at nitro dot med dot uc dot edu
2009-09-23 16:28 ` howarth at nitro dot med dot uc dot edu
2009-09-23 16:36 ` developer at sandoe-acoustics dot co dot uk
2009-09-23 16:51 ` howarth at nitro dot med dot uc dot edu
2009-09-23 17:53 ` howarth at nitro dot med dot uc dot edu
2009-09-23 18:41 ` howarth at nitro dot med dot uc dot edu
2009-09-23 18:57 ` howarth at nitro dot med dot uc dot edu
2009-09-23 20:44 ` mrs at apple dot com
2009-09-23 20:48 ` mrs at apple dot com
2009-09-23 20:49 ` mrs at apple dot com
2009-09-23 20:52 ` mrs at apple dot com
2009-09-23 21:06 ` howarth at nitro dot med dot uc dot edu
2009-09-23 21:18 ` howarth at nitro dot med dot uc dot edu
2009-09-23 23:45 ` howarth at nitro dot med dot uc dot edu
2009-09-24 7:47 ` developer at sandoe-acoustics dot co dot uk [this message]
2009-09-24 13:06 ` howarth at nitro dot med dot uc dot edu
2009-09-24 13:15 ` howarth at nitro dot med dot uc dot edu
2009-09-24 20:55 ` developer at sandoe-acoustics dot co dot uk
2009-09-24 22:33 ` howarth at nitro dot med dot uc dot edu
2009-09-24 22:42 ` developer at sandoe-acoustics dot co dot uk
2009-09-24 23:47 ` howarth at nitro dot med dot uc dot edu
2009-09-24 23:48 ` howarth at nitro dot med dot uc dot edu
2009-09-25 1:20 ` howarth at nitro dot med dot uc dot edu
2009-09-25 2:19 ` howarth at nitro dot med dot uc dot edu
2009-09-25 10:07 ` developer at sandoe-acoustics dot co dot uk
2009-09-25 10:45 ` howarth at nitro dot med dot uc dot edu
2009-09-25 10:54 ` developer at sandoe-acoustics dot co dot uk
2009-09-25 19:17 ` howarth at nitro dot med dot uc dot edu
2009-09-25 19:25 ` developer at sandoe-acoustics dot co dot uk
2009-09-25 23:52 ` howarth at nitro dot med dot uc dot edu
2009-09-26 0:54 ` howarth at nitro dot med dot uc dot edu
2009-09-26 1:00 ` howarth at nitro dot med dot uc dot edu
2009-09-26 2:55 ` howarth at nitro dot med dot uc dot edu
2009-09-26 5:51 ` howarth at nitro dot med dot uc dot edu
2009-09-26 17:29 ` developer at sandoe-acoustics dot co dot uk
2009-09-26 20:36 ` howarth at nitro dot med dot uc dot edu
2009-09-28 7:48 ` developer at sandoe-acoustics dot co dot uk
2009-09-28 9:02 ` developer at sandoe-acoustics dot co dot uk
2009-09-30 16:58 ` developer at sandoe-acoustics dot co dot uk
2009-09-30 19:46 ` mrs at apple dot com
2009-09-30 19:54 ` developer at sandoe-acoustics dot co dot uk
2009-09-30 23:36 ` howarth at nitro dot med dot uc dot edu
2009-09-30 23:38 ` howarth at nitro dot med dot uc dot edu
2009-10-01 8:36 ` developer at sandoe-acoustics dot co dot uk
2009-10-01 14:00 ` howarth at nitro dot med dot uc dot edu
2009-10-01 17:22 ` developer at sandoe-acoustics dot co dot uk
2009-10-01 19:18 ` mrs at apple dot com
2009-10-02 8:17 ` developer at sandoe-acoustics dot co dot uk
2009-10-02 10:39 ` developer at sandoe-acoustics dot co dot uk
2009-11-18 7:36 ` andreast at gcc dot gnu dot org
2009-11-18 7:37 ` andreast at gcc dot gnu dot org
2010-01-22 9:59 ` developer at sandoe-acoustics dot co dot uk
2010-03-11 3:30 ` howarth at nitro dot med dot uc dot edu
2010-03-11 12:18 ` ubizjak at gmail 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=20090924074647.31278.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).