From owner-freebsd-arch@FreeBSD.ORG Thu May 1 08:53:44 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D09E537B401; Thu, 1 May 2003 08:53:44 -0700 (PDT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A03743FAF; Thu, 1 May 2003 08:53:43 -0700 (PDT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.9/8.12.9) with ESMTP id h41Frgnd055311; Thu, 1 May 2003 19:53:42 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.9/8.12.9/Submit) id h41FrgT5055310; Thu, 1 May 2003 19:53:42 +0400 (MSD) Date: Thu, 1 May 2003 19:53:42 +0400 From: "Andrey A. Chernov" To: "Jacques A. Vidrine" , freebsd-arch@FreeBSD.org Message-ID: <20030501155342.GA55078@nagual.pp.ru> References: <20030430143121.GK39658@survey.codeburst.net> <20030430152708.GA26216@madman.celabo.org> <20030430153645.GL39658@survey.codeburst.net> <20030430164135.GB26508@madman.celabo.org> <20030501140255.GB1869@survey.codeburst.net> <20030501143032.GA34163@madman.celabo.org> <20030501144600.GC1869@survey.codeburst.net> <20030501145345.GA34884@madman.celabo.org> <20030501151458.GA54182@nagual.pp.ru> <20030501152251.GB34992@madman.celabo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030501152251.GB34992@madman.celabo.org> User-Agent: Mutt/1.5.4i Subject: Re: `Hiding' libc symbols X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 15:53:45 -0000 On Thu, May 01, 2003 at 10:22:51 -0500, Jacques A. Vidrine wrote: > > I'm with you ... as long as: So, we can right now back out strlcpy hack at least to minimize future work. It have nothing common with threads, namespace.h is for. Saving libc but not saving other libs application can be linked to gains really nothing. > (a) We then post-process libraries (or object files) to > automagically handle the symbols (all of them, or maybe just > those not covered by some standard we pick in the case of libc). > e.g. something such as > objcopy --weaken ${.IMPSRC} ${.TARGET} > but a bit more work. Ok. > (b) We give Daniel and others working on threaded libraries a chance > to discuss the special needs there. (That _is_ why namespace.h > was originally created. We do need to handle stubs somehow; weak > symbols alone are not enough.) See my another reply (to Daniel) about threads. > (c) We do it after 5.1-RELEASE, and before 5.2-RELEASE; or we only > do it in 6.x. Ok. > (d) I don't have to do it all. I too. :-) Most of work will be to change current threads tricks to prevent them be explotable from outside of libc/libc_r/etc, i.e. to be true internal. It is for our threads team who introduce namespace.h