From owner-cvs-src@FreeBSD.ORG Sun Aug 31 22:59:46 2003 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E7EF716A4BF; Sun, 31 Aug 2003 22:59:46 -0700 (PDT) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C9C043FE9; Sun, 31 Aug 2003 22:59:42 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: from freebsd1.cimlogic.com.au (localhost.cimlogic.com.au [127.0.0.1]) by cimlogic.com.au (8.12.9/8.12.9) with ESMTP id h8161LvD004933; Mon, 1 Sep 2003 16:01:21 +1000 (EST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.12.9/8.12.9/Submit) id h8161KZF004932; Mon, 1 Sep 2003 16:01:21 +1000 (EST) Date: Mon, 1 Sep 2003 16:01:20 +1000 From: John Birrell To: deischen@FreeBSD.org Message-ID: <20030901160120.A1311@freebsd1.cimlogic.com.au> References: <20030901045513.GA91654@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from eischen@vigrid.com on Mon, Sep 01, 2003 at 01:22:47AM -0400 cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org cc: David O'Brien Subject: Re: cvs commit: src/contrib/gcc/config freebsd-spec.h X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Sep 2003 05:59:47 -0000 On Mon, Sep 01, 2003 at 01:22:47AM -0400, Daniel Eischen wrote: > > {Net,Open}BSD and Linux all accept the "-pthread" option. By removing > > support for it we are the odd man out on accepted GCC options. You also > > {Net,Open}BSD have it because they had the same problem with > libc_r (it couldn't be linked with libc). Since when did Linux > get this hack and why? When the -pthread argument was added to FreeBSD's gcc, it was because the initial thread work wasn't allowed to 'touch' libc. That was off-limits. Times have changed and it's time we moved on from that position. Once libc was 'allowed' to have stubs in it for thread-specific data, mutexes, condition variables, etc, there was no need to have a separate library. I don't remember any of the operating systems mentioned having -pthread back then. Perhaps my memory is vague. That fact that they have it now is nothing more than a curiosity IMO. > Are we talking about buildworld or ports? I know we are > breaking 3rd party makefiles, but we need to do that > and knew over 2 years ago. If we're talking about things in 5.X that affect third party developers, let me say that a compiler option is the least of the problems they will encounter. I'm going through that 'little' exercise now. And what fun it is. Not. FWIW (probably not much), I support Dan's position on this. I'd like to see kse become the default as a true libpthread as has been assumed in all the work that those guys have done. I'll go one step further and say that I don't think libthr should be in the tree. And libc_r should be shot just as soon as kse is functional on the tier-1 platforms. -- John Birrell