From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/6396 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: the prototype decl of memcpy/memcmp/calloc/free should not in sched.h Date: Thu, 30 Oct 2014 23:24:10 -0400 Message-ID: <20141031032410.GZ22465@brightrain.aerifal.cx> References: Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1414725886 12706 80.91.229.3 (31 Oct 2014 03:24:46 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 31 Oct 2014 03:24:46 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-6409-gllmg-musl=m.gmane.org@lists.openwall.com Fri Oct 31 04:24:33 2014 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1Xk2p7-0000gl-GB for gllmg-musl@m.gmane.org; Fri, 31 Oct 2014 04:24:25 +0100 Original-Received: (qmail 9252 invoked by uid 550); 31 Oct 2014 03:24:23 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 9237 invoked from network); 31 Oct 2014 03:24:23 -0000 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:6396 Archived-At: On Fri, Oct 31, 2014 at 11:03:35AM +0800, 黄建忠 wrote: > Hi, there, > > sched.h in musl should not contains the prototype declarations of "memcpy/memcmp/calloc/free" func. > > memcpy/memcmp already in string.h > calloc/free already in stdlib.h > > Any reason they should exist in sched.h? They're present only under _GNU_SOURCE mode, and the reason is that musl's CPU_* macros for working with cpu sets for affinity use these functions directly rather than having additional exported symbols in a protected namespace to do the work. Is this approach causing a problem for you? Rich