public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Roland McGrath <roland@frob.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
	Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Nuke another 21 .plt slots
Date: Mon, 05 Aug 2002 15:18:00 -0000	[thread overview]
Message-ID: <20020806001731.O20867@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <20020805221155.C64591BA1B@perdition.linnaean.org>; from roland@frob.com on Mon, Aug 05, 2002 at 06:11:55PM -0400

On Mon, Aug 05, 2002 at 06:11:55PM -0400, Roland McGrath wrote:
> Thanks!  I put those in.  However, my PLT count does not match yours.  I
> get 169 in a build with TLS support, and I think that is only one more than
> without TLS.
> 
> I have been counting using this script (it gives a list of symbols; pipe it
> to wc -l), which counts only PLT slots for symbols defined in libc itself,
> and omits the malloc functions that are explicit exceptions.  That count is
> now 121.
> 
> #!/bin/sh
> 
> goodones='__libc_free
> __libc_malloc
> __libc_memalign
> __libc_realloc
> free
> calloc
> malloc
> realloc'

This list is too short, e.g. __fork and some others which are to
be overridden by libpthread.so should be in the list too.

> readelf -rW libc.so | awk '/JUMP_SLOT/ && $4 != "00000000" { print $5 }' |
> fgrep -vx "$goodones" | sort

I believe the difference can be that my build was with -O3, so a bunch
of calls were inlined and thus not going externally.
I'll try an -O2 build tomorrow.

	Jakub

  reply	other threads:[~2002-08-05 22:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-05 14:54 Jakub Jelinek
2002-08-05 15:11 ` Roland McGrath
2002-08-05 15:18   ` Jakub Jelinek [this message]
2002-08-05 15:21     ` Roland McGrath
2002-08-05 15:42       ` Ulrich Drepper
2002-08-05 23:20         ` Jakub Jelinek
2002-08-05 23:43           ` Ulrich Drepper
2002-08-06  0:08             ` Roland McGrath
2002-08-06  0:10               ` Roland McGrath
2002-08-06  0:19               ` Ulrich Drepper

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=20020806001731.O20867@sunsite.ms.mff.cuni.cz \
    --to=jakub@redhat.com \
    --cc=drepper@redhat.com \
    --cc=libc-hacker@sources.redhat.com \
    --cc=roland@frob.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).