From owner-freebsd-stable@FreeBSD.ORG Fri Feb 10 23:00:39 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74D9616A420 for ; Fri, 10 Feb 2006 23:00:39 +0000 (GMT) (envelope-from conrads@cox.net) Received: from eastrmmtao05.cox.net (eastrmmtao05.cox.net [68.230.240.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9868943D49 for ; Fri, 10 Feb 2006 23:00:38 +0000 (GMT) (envelope-from conrads@cox.net) Received: from serene.no-ip.org ([68.14.59.177]) by eastrmmtao05.cox.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20060210230042.RSEI14098.eastrmmtao05.cox.net@serene.no-ip.org> for ; Fri, 10 Feb 2006 18:00:42 -0500 Received: from serene.no-ip.org (localhost [127.0.0.1]) by serene.no-ip.org (8.13.4/8.13.4) with ESMTP id k1AN0NLW069494 for ; Fri, 10 Feb 2006 17:00:24 -0600 (CST) (envelope-from conrads@serene.no-ip.org) Received: (from conrads@localhost) by serene.no-ip.org (8.13.4/8.13.4/Submit) id k1AN0Ibw069493 for freebsd-stable@freebsd.org; Fri, 10 Feb 2006 17:00:18 -0600 (CST) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 10 Feb 2006 17:00:18 -0600 (CST) From: Conrad Sabatier To: freebsd-stable@freebsd.org Subject: CFLAGS in libc_r, libpthread and libthr, and MUTEX stuff in kern_mutex.c X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2006 23:00:39 -0000 Given that STABLE is supposed to be...well...*stable* :-) ... Could we possibly remove "-D_PTHREADS_INVARIANTS", "-D_LOCK_DEBUG" and "-g" from the CFLAGS in the Makefiles for libc_r, libpthread and libthr? I've been under the impression that these options were only intended for testing/debugging under CURRENT. Granted, it's a simple matter to patch the Makefiles after an update/before a buildworld, but it would be nice not to have to do so. On a related note, I was rather surprised to discover recently that in sys/kern/kern_mutex.c, the MUTEX_WAKE_ALL option is forcibly defined if not already defined in the user's kernel config. While the accompanying comment (in mutex.c) would seem to indicate that there's good reason for doing so at this time, at the very least, this should be documented in sys/conf/NOTES as well. Additionally, it should also be made unmistakably clear that certain other mutex-related options -- namely, ADAPTIVE_GIANT and NO_ADAPTIVE_MUTEXES -- have absolutely no effect whatsoever unless SMP is also defined. While I suppose this might be inferred from the fact that they're listed under the SMP section of NOTES, nonetheless, there is a chance that this relationship may go unrecognized. Thank you. -- Conrad J. Sabatier -- "In Unix veritas"