From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/6692 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: pthread_equal Date: Mon, 8 Dec 2014 09:56:04 -0500 Message-ID: <20141208145604.GC4574@brightrain.aerifal.cx> References: <1418049745.15892.10.camel@posteo.de> 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 1418050586 16309 80.91.229.3 (8 Dec 2014 14:56:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 8 Dec 2014 14:56:26 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-6705-gllmg-musl=m.gmane.org@lists.openwall.com Mon Dec 08 15:56:18 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 1XxzjW-0000lt-0X for gllmg-musl@m.gmane.org; Mon, 08 Dec 2014 15:56:18 +0100 Original-Received: (qmail 5744 invoked by uid 550); 8 Dec 2014 14:56:16 -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 5734 invoked from network); 8 Dec 2014 14:56:16 -0000 Content-Disposition: inline In-Reply-To: <1418049745.15892.10.camel@posteo.de> User-Agent: Mutt/1.5.21 (2010-09-15) Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:6692 Archived-At: On Mon, Dec 08, 2014 at 03:42:25PM +0100, Jörg Krause wrote: > Why does musl declares pthread_equal both as macro and as function? C and POSIX allow any of their standard functions to be provided as macros too, but the function definition must always be provided. The reason I put the macro in musl is simply that it's easy to do and gives better code (trivial inline comparison rather than spilling all registers and making a function call) and it's not something where the implementation could change or need to change. Rich