public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>,
	arjanv@redhat.com, rth@redhat.com
Subject: Re: [PATCH] glibc part of stack protector (take 2)
Date: Sun, 26 Jun 2005 18:22:00 -0000	[thread overview]
Message-ID: <42BEF204.1000007@redhat.com> (raw)
In-Reply-To: <20050625085455.GD7663@sunsite.mff.cuni.cz>

[-- Attachment #1: Type: text/plain, Size: 921 bytes --]

I applied the patch.

But not the LinuxThreads part.  In fact, once I have the time (probably
the week after next) LT will be removed from the trunk of the CVS
archive.  This has *loooong* been announced.  We cannot carry forward
that crappy code forever.  And the 2.4 release is the time to make the
break.  Programs will know when they cannot run with LT if they
reference symbols with version GLIBC_2.4.  The code base still exists on
the 2.3 branch so there is always the possibility to

a) use 2.3 outright, since Roland still backports patches

and

b) people can build a separate glibc with its own ld.so for desperate LT
users.

At the same time I'll likely remove the non-TLS support.  That's a
wakeup call for the Hurd people: get moving with implementing the
support.  It's been now almost 3 years.

-- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

      reply	other threads:[~2005-06-26 18:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-23 22:25 [RFC PATCH] glibc part of stack protector Jakub Jelinek
2005-06-24 15:14 ` Ulrich Drepper
2005-06-25  8:55   ` [PATCH] glibc part of stack protector (take 2) Jakub Jelinek
2005-06-26 18:22     ` Ulrich Drepper [this message]

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=42BEF204.1000007@redhat.com \
    --to=drepper@redhat.com \
    --cc=arjanv@redhat.com \
    --cc=jakub@redhat.com \
    --cc=libc-hacker@sources.redhat.com \
    --cc=rth@redhat.com \
    /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).