From: Ulrich Drepper <drepper@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Kill 27 .rel{,a}.plt dynamic relocations in my i686 glibc build (mainly sunrpc)
Date: Tue, 14 May 2002 17:25:00 -0000 [thread overview]
Message-ID: <1021422319.2824.19.camel@myware.mynet> (raw)
In-Reply-To: <20020511235200.H1551@sunsite.ms.mff.cuni.cz>
[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]
On Sat, 2002-05-11 at 14:52, Jakub Jelinek wrote:
> The following patch kills a bunch of dynamic PLT relocations, mainly
> in sunrpc.
Thanks, I've applied the patch. Although I see 26 plts go...
> (it is of course a JDK bug too, as it should handle unknown
> fds properly, but anyway).
I've told somebody at Sun about this and hopefully they stop writing
such stupid code in future.
> IMHO we should cook up a list of symbols libraries should be able to
> interpose (definitely all malloc functions, etc.) and kill the rest.
That's the intention. So far I only have a few symbols which need to be
kept. The malloc functions are the only official ones. There are a few
more internal symbols.
I'll try to create a list of those which need to go. Hopefully this
will encourage people to help finishing the work. This is a very
time-consuming work which is why I haven't done all that already.
--
---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2002-05-15 0:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-11 14:59 Jakub Jelinek
2002-05-14 17:25 ` 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=1021422319.2824.19.camel@myware.mynet \
--to=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.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).