Date: Wed, 9 May 2018 00:38:55 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Phil Shafer <phil@juniper.net> Cc: freebsd-arch@freebsd.org Subject: Re: initialization problem w/ thread-specific .tbss data on i386 Message-ID: <20180508213855.GS6887@kib.kiev.ua> In-Reply-To: <201805082131.w48LVvBo071075@idle.juniper.net> References: <20180508081417.GL6887@kib.kiev.ua> <201805082131.w48LVvBo071075@idle.juniper.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 08, 2018 at 05:31:57PM -0400, Phil Shafer wrote: > Konstantin Belousov writes: > >Also, try to link in libpthread. > > This was interesting, not that I'm sure what it means: > > % env LD_PRELOAD=/usr/lib/libpthread.so /tmp/uptime > 5:26PM up 4 days, 9:22, 3 users, load averages: 0.55, 0.52, 0.51 > > (where /tmp/uptime is a symlink to /usr/obj/.../w/w). > (see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227552) > > Does the mean that the use of __thread requires -lpthread? My > understanding was that the startup code handled thread-specific > data for the main thread of execution. No, try to compile libc with e.g. clang 5 and see if it also fixes libxo.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180508213855.GS6887>