Date: Tue, 29 Jan 2013 23:16:00 +0100 From: Marius Strobl <marius@alchemy.franken.de> To: Konstantin Belousov <kostikbel@gmail.com> Cc: current@freebsd.org Subject: Re: Fast gettimeofday(2) and static linking Message-ID: <20130129221600.GG85306@alchemy.franken.de> In-Reply-To: <20130128155524.GS2522@kib.kiev.ua> References: <20130125123554.GQ2522@kib.kiev.ua> <20130128154516.GA59472@alchemy.franken.de> <20130128155524.GS2522@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 28, 2013 at 05:55:24PM +0200, Konstantin Belousov wrote: > On Mon, Jan 28, 2013 at 04:45:17PM +0100, Marius Strobl wrote: > > On Fri, Jan 25, 2013 at 02:35:54PM +0200, Konstantin Belousov wrote: > > > Bruce Evans reported that statically linked binaries on HEAD an stable/9 > > > use the syscall for gettimeofday(2) and clock_gettime(2). Apparently, this > > > is due to my use of the weak reference to the __vdso* symbols in the > > > libc implementations. > > > > > > Patch below reworks the __vdso* attributes to only make the symbols > > > weak, but keep the references strong. Since I have to add a stub for > > > each architecture, I would like to ask non-x86 machines owners to test > > > the patch. > > > > > > > Hi Konstantin, > > > > what's the appropriate way to test this? > > Please rebuild the world with the patch and check that gettimeofday(2) still > works on your architecture, both for the static and dynamic binaries. > I think that just booting multiuser is enough. Okay, looks good on sparc64 (tested with a dynamically as well as a statically built time(1)). Marius
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130129221600.GG85306>