From owner-freebsd-arch@FreeBSD.ORG Mon Mar 12 01:18:16 2012 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 10EA9106566C; Mon, 12 Mar 2012 01:18:16 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from fallbackmx10.syd.optusnet.com.au (fallbackmx10.syd.optusnet.com.au [211.29.132.251]) by mx1.freebsd.org (Postfix) with ESMTP id 7F4DC8FC0C; Mon, 12 Mar 2012 01:18:15 +0000 (UTC) Received: from mail07.syd.optusnet.com.au (mail07.syd.optusnet.com.au [211.29.132.188]) by fallbackmx10.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id q2C1IEUQ013752; Mon, 12 Mar 2012 12:18:14 +1100 Received: from c211-30-171-136.carlnfd1.nsw.optusnet.com.au (c211-30-171-136.carlnfd1.nsw.optusnet.com.au [211.30.171.136]) by mail07.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id q2C1I3t3018913 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Mar 2012 12:18:04 +1100 Date: Mon, 12 Mar 2012 12:18:02 +1100 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Adrian Chadd In-Reply-To: Message-ID: <20120312120436.H1098@besplex.bde.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-arch@freebsd.org, Robert Millan Subject: Re: [PATCH] Add compatibility X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2012 01:18:16 -0000 On Sun, 11 Mar 2012, Adrian Chadd wrote: > I agree we should move them out of the namespace. I'd even suggest > prefixing them with something BSD specific, as two underscores may not > be enough of a hint. No, they are already outside of the user namespace. cpufunc.h is a kernel header that just happens to be abusable in userland. Though I originally intended it to be usable in userland. 2 underscores would make any use undefined, but no more than most uses already are. > That requires some sweeping changes of userland code, but I think it's > for the best. This would be mostly churn in the downwards direction. I just checked the API in old DOS compilers. In Turbo C it is: #include void outportb(int portid, unsigned char value); [outportb is normally a macro that expands to an inline asm function.] So there is no conflict with this API, since its name is different. Bruce