public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Lynch <Nathan_Lynch@mentor.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Andy Lutomirski <luto@kernel.org>,
	Anton Blanchard <anton@samba.org>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Chris Metcalf <cmetcalf@tilera.com>,
	Richard Kuo <rkuo@codeaurora.org>, X86 ML <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Isaac Dunham <ibid.ag@gmail.com>, Rich Felker <dalias@libc.org>,
	"musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: Re: [PATCH] x86/vdso: Emit a GNU hash
Date: Fri, 7 Aug 2015 11:10:34 -0500	[thread overview]
Message-ID: <55C4D87A.2030101@mentor.com> (raw)
In-Reply-To: <CALCETrX3izAp_Gzv3oc0srrTPYRDz=B1U-5YYwiqVHgW_s0v5A@mail.gmail.com>

On 08/06/2015 05:52 PM, Andy Lutomirski wrote:
> [adding lots of cc's]
> 
> On Thu, Aug 6, 2015 at 2:45 PM, Andy Lutomirski <luto@kernel.org> wrote:
>> From: Andy Lutomirski <luto@amacapital.net>
>>
>> Some dynamic loaders may be slightly faster if a GNU hash is
>> available.  Strangely, this seems to have no effect at all on the
>> vdso size.

FWIW, I see arch/x86/entry/vdso/vdso64.so increase by 168 bytes here,
using GCC 4.9.2, Binutils 2.24 as packaged by Fedora 21.

I see a similar increase when I make the equivalent change for ARM.



  parent reply	other threads:[~2015-08-07 16:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06 21:45 [PATCH] x86/vdso: Emit a GNU hash Andy Lutomirski
2015-08-06 22:52 ` Andy Lutomirski
2015-08-07  0:48   ` [PATCH] tile/vdso: emit a GNU hash as well Chris Metcalf
2015-08-07  7:02   ` [PATCH] s390/vdso: emit a GNU hash Martin Schwidefsky
2015-08-07 16:10   ` Nathan Lynch [this message]
2015-08-07 18:13     ` [PATCH] x86/vdso: Emit " Andy Lutomirski
2015-08-09 10:25 ` [tip:x86/asm] " tip-bot for Andy Lutomirski

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=55C4D87A.2030101@mentor.com \
    --to=nathan_lynch@mentor.com \
    --cc=anton@samba.org \
    --cc=cmetcalf@tilera.com \
    --cc=dalias@libc.org \
    --cc=ibid.ag@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=luto@kernel.org \
    --cc=musl@lists.openwall.com \
    --cc=rkuo@codeaurora.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=x86@kernel.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