Date: Mon, 19 Nov 2018 15:34:16 -0500 From: Ed Maste <emaste@freebsd.org> To: Shawn Webb <shawn.webb@hardenedbsd.org> Cc: src-committers <src-committers@freebsd.org>, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r340640 - head/lib/libc Message-ID: <CAPyFy2BNj89uQmfyVOrGXPWeZVhoYDJ00ihjQQnUqrVkg6O0-Q@mail.gmail.com> In-Reply-To: <20181119193810.b4mexvznrqyb7j7v@mutt-hbsd> References: <201811191812.wAJICdFf087392@repo.freebsd.org> <20181119193810.b4mexvznrqyb7j7v@mutt-hbsd>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 19 Nov 2018 at 14:38, Shawn Webb <shawn.webb@hardenedbsd.org> wrote: > > Since the use of ifunc in libc is only applicable to amd64, I wonder > if it would be best to disable BIND_NOW in > lib/libc/amd64/Makefile.inc. I don't believe there's any need to > disable BIND_NOW for libc on other architectures. At least arm64 and i386 will probably start making use of ifuncs in the not-too-distant future. After some more investigation and if we're sure that it's only ifuncs that are affected this might be made machine-dependent.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2BNj89uQmfyVOrGXPWeZVhoYDJ00ihjQQnUqrVkg6O0-Q>