From owner-freebsd-standards@FreeBSD.ORG Mon Aug 29 11:02:23 2005 Return-Path: X-Original-To: freebsd-standards@freebsd.org Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D22E616A420 for ; Mon, 29 Aug 2005 11:02:23 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6867E43D5D for ; Mon, 29 Aug 2005 11:02:19 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7TB2J0u021667 for ; Mon, 29 Aug 2005 11:02:19 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7TB2Ihm021661 for freebsd-standards@freebsd.org; Mon, 29 Aug 2005 11:02:18 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 29 Aug 2005 11:02:18 GMT Message-Id: <200508291102.j7TB2Ihm021661@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-standards@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 11:02:24 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/03/05] bin/25542 standards /bin/sh: null char in quoted string o [2002/12/13] kern/46239 standards posix semaphore implementation errors o [2003/04/21] standards/51209standards [PATCH] add a64l()/l64a/l64a_r functions o [2003/07/12] standards/54410standards one-true-awk not POSIX compliant (no exte o [2004/11/03] standards/73500standards 'set +o' in /bin/sh does not include unse o [2005/06/25] standards/82654standards C99 long double math functions are missin o [2005/08/04] standards/84539standards [ patch ] add support of -V and -v args f 7 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/09/24] bin/21519 standards sys/dir.h should be deprecated some more o [2001/01/16] bin/24390 standards Replacing old dir-symlinks when using /bi s [2001/01/24] standards/24590standards timezone function not compatible witn Sin s [2001/06/18] kern/28260 standards UIO_MAXIOV needs to be made public p [2001/11/20] standards/32126standards getopt(3) not Unix-98 conformant s [2002/03/19] standards/36076standards Implementation of POSIX fuser command o [2002/06/14] standards/39256standards [v]snprintf aren't POSIX-conformant for s p [2002/08/12] standards/41576standards POSIX compliance of ln(1) o [2002/10/23] standards/44425standards getcwd() succeeds even if current dir has o [2002/12/09] standards/46119standards Priority problems for SCHED_OTHER using p o [2003/07/24] standards/54809standards pcvt deficits o [2003/07/25] standards/54833standards more pcvt deficits o [2003/07/25] standards/54839standards pcvt deficits o [2003/07/31] standards/55112standards glob.h, glob_t's gl_pathc should be "size o [2003/09/05] standards/56476standards cd9660 unicode support simple hack o [2003/10/29] standards/58676standards grantpt(3) alters storage used by ptsname s [2004/02/14] standards/62858standards malloc(0) not C99 compliant p [2004/02/21] standards/63173standards Patch to add getopt_long_only(3) to libc o [2004/03/29] kern/64875 standards [patch] add a system call: fdatasync() o [2004/05/07] standards/66357standards make POSIX conformance problem ('sh -e' & o [2004/05/11] standards/66531standards _gettemp uses a far smaller set of filena o [2004/08/22] standards/70813standards [PATCH] ls not Posix compliant o [2004/08/26] docs/70985 standards [patch] sh(1): incomplete documentation o o [2004/09/22] standards/72006standards floating point formating in non-C locales o [2005/03/20] standards/79055standards Add an IFS regression test for shells o [2005/03/20] standards/79056standards regex(3) regression tests o [2005/03/21] standards/79067standards /bin/sh should be more intelligent about o [2005/05/20] standards/81287standards [PATCH]: fingerd(8) might send a line not o [2005/07/21] standards/83845standards [ patch ] add log2() and log2f() support o [2005/08/18] standards/85080standards output of long double subnormals (with pr o [2005/08/18] standards/85090standards [patch] add memalign() and posix_memalign 31 problems total. From owner-freebsd-standards@FreeBSD.ORG Tue Aug 30 08:20:18 2005 Return-Path: X-Original-To: freebsd-standards@hub.freebsd.org Delivered-To: freebsd-standards@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 34D6F16A41F for ; Tue, 30 Aug 2005 08:20:18 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A860043D5C for ; Tue, 30 Aug 2005 08:20:17 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7U8KHta092633 for ; Tue, 30 Aug 2005 08:20:17 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7U8KHAf092632; Tue, 30 Aug 2005 08:20:17 GMT (envelope-from gnats) Date: Tue, 30 Aug 2005 08:20:17 GMT Message-Id: <200508300820.j7U8KHAf092632@freefall.freebsd.org> To: freebsd-standards@FreeBSD.org From: Sergey Matveychuk Cc: Subject: Re: standards/85090: [patch] add memalign() and posix_memalign() functions X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Sergey Matveychuk List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 08:20:18 -0000 The following reply was made to PR standards/85090; it has been noted by GNATS. From: Sergey Matveychuk To: bug-followup@FreeBSD.org Cc: Stefan Farfeleder Subject: Re: standards/85090: [patch] add memalign() and posix_memalign() functions Date: Tue, 30 Aug 2005 12:13:47 +0400 > - Do we really need memalign()? It looks rather obsolete. I'm not sure really. posix_memalign() is advanced standard extension, but memalign() is not standard at all, but widely used (in a Linux world at least). It could be removed from the patch. But posix_memalign() has a quite strange semantics. Like all other posix_ function have :) -- Sem. From owner-freebsd-standards@FreeBSD.ORG Tue Aug 30 08:20:21 2005 Return-Path: X-Original-To: freebsd-standards@hub.freebsd.org Delivered-To: freebsd-standards@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76E9716A420 for ; Tue, 30 Aug 2005 08:20:21 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FFB243D55 for ; Tue, 30 Aug 2005 08:20:21 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7U8KLQf092641 for ; Tue, 30 Aug 2005 08:20:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7U8KK1E092640; Tue, 30 Aug 2005 08:20:20 GMT (envelope-from gnats) Date: Tue, 30 Aug 2005 08:20:20 GMT Message-Id: <200508300820.j7U8KK1E092640@freefall.freebsd.org> To: freebsd-standards@FreeBSD.org From: Sergey Matveychuk Cc: Subject: Re: standards/85090: [patch] add memalign() and posix_memalign() functions X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Sergey Matveychuk List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 08:20:21 -0000 The following reply was made to PR standards/85090; it has been noted by GNATS. From: Sergey Matveychuk To: bug-followup@FreeBSD.org, sem@FreeBSD.org Cc: Subject: Re: standards/85090: [patch] add memalign() and posix_memalign() functions Date: Tue, 30 Aug 2005 12:18:51 +0400 BTW, posix_memalign() should be marked as IEEE Std 1003.1-2001 compliant on man page. -- Sem. From owner-freebsd-standards@FreeBSD.ORG Tue Aug 30 08:30:55 2005 Return-Path: X-Original-To: standards@FreeBSD.org Delivered-To: freebsd-standards@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DEA616A41F; Tue, 30 Aug 2005 08:30:55 +0000 (GMT) (envelope-from sem@FreeBSD.org) Received: from relay-er5.mbrd.ru (relay-er5.mbrd.ru [194.117.71.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE48843D46; Tue, 30 Aug 2005 08:30:54 +0000 (GMT) (envelope-from sem@FreeBSD.org) Received: from msd.mbrd.ru ([172.16.4.9]) by relay-er5.mbrd.ru with esmtp (Exim 4.x) id 1EA1W8-000Ikd-4h; Tue, 30 Aug 2005 12:30:52 +0400 Message-ID: <4314193B.80208@FreeBSD.org> Date: Tue, 30 Aug 2005 12:30:51 +0400 From: Sergey Matveychuk User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: standards@FreeBSD.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: arch@FreeBSD.org Subject: standards/85090: [patch] add memalign() and posix_memalign() functions X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 08:30:55 -0000 Could I hear some comments, need we a memalign() function or not? -- Sem. From owner-freebsd-standards@FreeBSD.ORG Tue Aug 30 17:02:36 2005 Return-Path: X-Original-To: standards@freebsd.org Delivered-To: freebsd-standards@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 926DB16A41F; Tue, 30 Aug 2005 17:02:36 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B02B43D46; Tue, 30 Aug 2005 17:02:35 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id j7UH2Z2i021950; Tue, 30 Aug 2005 12:02:35 -0500 (CDT) (envelope-from dan) Date: Tue, 30 Aug 2005 12:02:35 -0500 From: Dan Nelson To: Sergey Matveychuk Message-ID: <20050830170235.GB4337@dan.emsphone.com> References: <4314193B.80208@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4314193B.80208@FreeBSD.org> X-OS: FreeBSD 5.4-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.9i Cc: arch@freebsd.org, standards@freebsd.org Subject: Re: standards/85090: [patch] add memalign() and posix_memalign() functions X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 17:02:36 -0000 In the last episode (Aug 30), Sergey Matveychuk said: > Could I hear some comments, need we a memalign() function or not? Our malloc already aligns pretty well. Blocks < 16 bytes are aligned to 16 bytes. Blocks from 16 to pagesize are aligned to powers of two (rounded up), and blocks greater than pagesize are aligned to pagesize. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-standards@FreeBSD.ORG Wed Aug 31 02:39:28 2005 Return-Path: X-Original-To: freebsd-standards@hub.freebsd.org Delivered-To: freebsd-standards@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7367216A429; Wed, 31 Aug 2005 02:39:28 +0000 (GMT) (envelope-from rodrigc@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF53443D5E; Wed, 31 Aug 2005 02:39:27 +0000 (GMT) (envelope-from rodrigc@FreeBSD.org) Received: from freefall.freebsd.org (rodrigc@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7V2dRje043032; Wed, 31 Aug 2005 02:39:27 GMT (envelope-from rodrigc@freefall.freebsd.org) Received: (from rodrigc@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7V2dRxs043028; Wed, 31 Aug 2005 02:39:27 GMT (envelope-from rodrigc) Date: Wed, 31 Aug 2005 02:39:27 GMT From: Craig Rodrigues Message-Id: <200508310239.j7V2dRxs043028@freefall.freebsd.org> To: rodrigc@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-standards@FreeBSD.org Cc: Subject: Re: standards/80293: sysconf() does not support well-defined unistd values X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 02:39:29 -0000 Synopsis: sysconf() does not support well-defined unistd values Responsible-Changed-From-To: freebsd-bugs->freebsd-standards Responsible-Changed-By: rodrigc Responsible-Changed-When: Wed Aug 31 02:38:17 GMT 2005 Responsible-Changed-Why: sysconf() is not a kernel function, moving this to standards http://www.freebsd.org/cgi/query-pr.cgi?pr=80293 From owner-freebsd-standards@FreeBSD.ORG Wed Aug 31 08:14:35 2005 Return-Path: X-Original-To: standards@freebsd.org Delivered-To: freebsd-standards@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A181716A41F; Wed, 31 Aug 2005 08:14:35 +0000 (GMT) (envelope-from sem@FreeBSD.org) Received: from relay-er5.mbrd.ru (relay-er5.mbrd.ru [194.117.71.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD9CC43D46; Wed, 31 Aug 2005 08:14:34 +0000 (GMT) (envelope-from sem@FreeBSD.org) Received: from msd.mbrd.ru ([172.16.4.9]) by relay-er5.mbrd.ru with esmtp (Exim 4.x) id 1EANjn-0001SE-TD; Wed, 31 Aug 2005 12:14:28 +0400 Message-ID: <431566E3.5040606@FreeBSD.org> Date: Wed, 31 Aug 2005 12:14:27 +0400 From: Sergey Matveychuk User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dan Nelson References: <4314193B.80208@FreeBSD.org> <20050830170235.GB4337@dan.emsphone.com> In-Reply-To: <20050830170235.GB4337@dan.emsphone.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: arch@freebsd.org, standards@freebsd.org Subject: Re: standards/85090: [patch] add memalign() and posix_memalign() functions X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 08:14:35 -0000 Dan Nelson wrote: > In the last episode (Aug 30), Sergey Matveychuk said: > >>Could I hear some comments, need we a memalign() function or not? > > > Our malloc already aligns pretty well. Blocks < 16 bytes are aligned > to 16 bytes. Blocks from 16 to pagesize are aligned to powers of two > (rounded up), and blocks greater than pagesize are aligned to pagesize. > Yes, I know. But if programmer needs some special align? There is posix_memalign() in standard (as extension). Need we posix_memalign() then? -- Sem. From owner-freebsd-standards@FreeBSD.ORG Thu Sep 1 09:49:36 2005 Return-Path: X-Original-To: freebsd-standards@freebsd.org Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDC7916A41F for ; Thu, 1 Sep 2005 09:49:36 +0000 (GMT) (envelope-from stb@lassitu.de) Received: from schlepper.zs64.net (schlepper.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EABB43D49 for ; Thu, 1 Sep 2005 09:49:35 +0000 (GMT) (envelope-from stb@lassitu.de) Received: from [IPv6:::1] (schlepper [212.12.50.230]) by schlepper.zs64.net (8.13.3/8.12.9) with ESMTP id j819nYt8035890 for ; Thu, 1 Sep 2005 11:49:34 +0200 (CEST) (envelope-from stb@lassitu.de) Mime-Version: 1.0 (Apple Message framework v734) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-standards@freebsd.org From: Stefan Bethke Date: Thu, 1 Sep 2005 11:49:33 +0200 X-Mailer: Apple Mail (2.734) Subject: xargs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2005 09:49:37 -0000 I've stumbled over the differing behavior of xargs when standard input delivers an immediate end of file: In recent versions of FreeBSD and OpenBSD, I get this: $ xargs echo foo The xargs utility shall construct a command line consisting of the > utility and argument operands specified followed by as many > arguments read in sequence from standard input as fit in length and > number constraints specified by the options. The xargs utility > shall then invoke the constructed command line and wait for its > completion. This sequence shall be repeated [...] I personally prefer the BSD behaviour, but I wonder whether anyone might rely on the SUSv3 behavior? I came across a makefile that assumed BSD behavior, but failed: find . -name "*.orig" | xargs rm because no orig files were found, but rm was executed anyway, with zero arguments. Stefan -- Stefan Bethke Fon +49 170 346 0140 From owner-freebsd-standards@FreeBSD.ORG Fri Sep 2 17:57:59 2005 Return-Path: X-Original-To: freebsd-standards@hub.freebsd.org Delivered-To: freebsd-standards@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55CB116A421; Fri, 2 Sep 2005 17:57:59 +0000 (GMT) (envelope-from rodrigc@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A38F43D45; Fri, 2 Sep 2005 17:57:59 +0000 (GMT) (envelope-from rodrigc@FreeBSD.org) Received: from freefall.freebsd.org (rodrigc@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j82HvxWV054850; Fri, 2 Sep 2005 17:57:59 GMT (envelope-from rodrigc@freefall.freebsd.org) Received: (from rodrigc@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j82HvxKB054846; Fri, 2 Sep 2005 17:57:59 GMT (envelope-from rodrigc) Date: Fri, 2 Sep 2005 17:57:59 GMT From: Craig Rodrigues Message-Id: <200509021757.j82HvxKB054846@freefall.freebsd.org> To: flashdict@gmail.com, rodrigc@FreeBSD.org, freebsd-standards@FreeBSD.org Cc: Subject: Re: standards/80293: sysconf() does not support well-defined unistd values X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 17:57:59 -0000 Synopsis: sysconf() does not support well-defined unistd values State-Changed-From-To: open->analyzed State-Changed-By: rodrigc State-Changed-When: Fri Sep 2 17:53:02 GMT 2005 State-Changed-Why: Whether or not a constant is defined in is not relevant to whether sysconf() accepts it or not (unfortunately). The list of constants supported by sysconf() are handled in /usr/src/lib/libc/gen/sysconf.c Any constant which is not handled there will return a -1, and set errno to EINVAL, which is legal behavior with respect to the Single Unix Specification. For _SC_GETGR_R_SIZE_MAX, it is difficult to return a single value, because in the file where this implemented ( /usr/src/lib/libc/gen/getgrgent.c ), the getgr*_r functions are delegated down to _nsdispatch(). http://www.freebsd.org/cgi/query-pr.cgi?pr=80293