From owner-freebsd-standards@FreeBSD.ORG Sun Apr 29 00:14:59 2007 Return-Path: X-Original-To: freebsd-standards@FreeBSD.org Delivered-To: freebsd-standards@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4C2CF16A400; Sun, 29 Apr 2007 00:14:59 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailout1.pacific.net.au (mailout1-3.pacific.net.au [61.8.2.210]) by mx1.freebsd.org (Postfix) with ESMTP id 1159A13C44B; Sun, 29 Apr 2007 00:14:59 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.2.163]) by mailout1.pacific.net.au (Postfix) with ESMTP id ADD995A0E45; Sun, 29 Apr 2007 10:14:57 +1000 (EST) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailproxy2.pacific.net.au (Postfix) with ESMTP id BBE0127407; Sun, 29 Apr 2007 10:14:56 +1000 (EST) Date: Sun, 29 Apr 2007 10:14:55 +1000 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: =?X-UNKNOWN?Q?Vincent_Lef=E8vre?= In-Reply-To: <200704271313.l3RDDLWw085017@www.freebsd.org> Message-ID: <20070429094705.J17746@delplex.bde.org> References: <200704271313.l3RDDLWw085017@www.freebsd.org> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-200284211-1177805695=:17746" Cc: freebsd-gnats-submit@FreeBSD.org, freebsd-standards@FreeBSD.org Subject: Re: standards/112180: tgamma on negative integers returns Inf instead of NaN 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: Sun, 29 Apr 2007 00:14:59 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-200284211-1177805695=:17746 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Fri, 27 Apr 2007, Vincent Lef=E8vre wrote: > Though POSIX allows an implementation-defined value to be returned, this = is mainly in the case where NaN is not supported, and NaN is the best choic= e and is what tgamma returns on other platforms (Linux, HP-UX, Mac OS X). Also, Annex F of C99 (about the IEEE-754/IEC-mumble binding) requires a NaN plus the "invalid" exception. Bruce --0-200284211-1177805695=:17746-- From owner-freebsd-standards@FreeBSD.ORG Sun Apr 29 00:20:10 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E6CEC16A400 for ; Sun, 29 Apr 2007 00:20:10 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 9594213C44C for ; Sun, 29 Apr 2007 00:20:10 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l3T0KAOb069041 for ; Sun, 29 Apr 2007 00:20:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l3T0KA0e069040; Sun, 29 Apr 2007 00:20:10 GMT (envelope-from gnats) Date: Sun, 29 Apr 2007 00:20:10 GMT Message-Id: <200704290020.l3T0KA0e069040@freefall.freebsd.org> To: freebsd-standards@FreeBSD.org From: Bruce Evans Cc: Subject: Re: standards/112180: tgamma on negative integers returns Inf instead of NaN X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bruce Evans List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2007 00:20:11 -0000 The following reply was made to PR standards/112180; it has been noted by GNATS. From: Bruce Evans To: =?X-UNKNOWN?Q?Vincent_Lef=E8vre?= Cc: freebsd-gnats-submit@FreeBSD.org, freebsd-standards@FreeBSD.org Subject: Re: standards/112180: tgamma on negative integers returns Inf instead of NaN Date: Sun, 29 Apr 2007 10:14:55 +1000 (EST) This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-200284211-1177805695=:17746 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Fri, 27 Apr 2007, Vincent Lef=E8vre wrote: > Though POSIX allows an implementation-defined value to be returned, this = is mainly in the case where NaN is not supported, and NaN is the best choic= e and is what tgamma returns on other platforms (Linux, HP-UX, Mac OS X). Also, Annex F of C99 (about the IEEE-754/IEC-mumble binding) requires a NaN plus the "invalid" exception. Bruce --0-200284211-1177805695=:17746-- From owner-freebsd-standards@FreeBSD.ORG Mon Apr 30 11:08:30 2007 Return-Path: X-Original-To: freebsd-standards@FreeBSD.org Delivered-To: freebsd-standards@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6FD8616A40A for ; Mon, 30 Apr 2007 11:08:30 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 5204213C45A for ; Mon, 30 Apr 2007 11:08:30 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l3UB8U3N007084 for ; Mon, 30 Apr 2007 11:08:30 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l3UB8ST7007080 for freebsd-standards@FreeBSD.org; Mon, 30 Apr 2007 11:08:28 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 30 Apr 2007 11:08:28 GMT Message-Id: <200704301108.l3UB8ST7007080@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon 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, 30 Apr 2007 11:08:30 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o bin/25542 standards /bin/sh: null char in quoted string o kern/46239 standards posix semaphore implementation errors o stand/54410 standards one-true-awk not POSIX compliant (no extended REs) o stand/82654 standards C99 long double math functions are missing o stand/94729 standards [libc] fcntl() throws undocumented ENOTTY 5 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o bin/21519 standards sys/dir.h should be deprecated some more o bin/24390 standards Replacing old dir-symlinks when using /bin/ln s stand/24590 standards timezone function not compatible witn Single Unix Spec s kern/28260 standards UIO_MAXIOV needs to be made public s stand/36076 standards Implementation of POSIX fuser command o stand/39256 standards snprintf/vsnprintf aren't POSIX-conformant for strings p stand/41576 standards POSIX compliance of ln(1) o stand/44425 standards getcwd() succeeds even if current dir has perm 000. o stand/46119 standards Priority problems for SCHED_OTHER using pthreads o stand/54833 standards [pcvt] more pcvt deficits o stand/54839 standards [pcvt] pcvt deficits p stand/55112 standards glob.h, glob_t's gl_pathc should be "size_t", not "int o stand/56476 standards cd9660 unicode support simple hack o stand/58676 standards grantpt(3) alters storage used by ptsname(3) s stand/62858 standards malloc(0) not C99 compliant s kern/64875 standards [libc] [patch] [feature request] add a system call: fd o stand/66357 standards make POSIX conformance problem ('sh -e' & '+' command- o stand/66531 standards _gettemp uses a far smaller set of filenames than docu o stand/70813 standards [PATCH] ls(1) not Posix compliant o stand/72006 standards floating point formating in non-C locales o stand/79056 standards regex(3) regression tests a stand/80293 standards sysconf() does not support well-defined unistd values o stand/81287 standards [PATCH]: fingerd(8) might send a line not ending in CR o stand/83845 standards [libm] [patch] add log2() and log2f() support for libm o stand/85080 standards output of long double subnormals (with printf) is wron o stand/92360 standards [headers] [patch] Missing TAB3 in kernel headers o stand/92362 standards [headers] [patch] Missing SIGPOLL in kernel headers o kern/93705 standards [headers] [patch] ENODATA and EGREGIOUS (for glibc com o stand/96016 standards [headers] clock_getres et al should be in o stand/96236 standards [PATCH] [POSIX] sed.1 incorrectly describes a function p stand/99517 standards Missing SIGRTMIN and SIGRTMAX signals o stand/99960 standards [Patch] make(1): Add -p flag o stand/100017 standards [Patch] Add fuser(1) functionality to fstat(1) o stand/104743 standards [headers] [patch] Wrong values for _POSIX_ minimal lim o stand/104841 standards [libm] [patch] C99 long double square root. o stand/107561 standards [patch] Missing SUS function tcgetsid() o stand/112180 standards tgamma on negative integers returns Inf instead of NaN 37 problems total. From owner-freebsd-standards@FreeBSD.ORG Sat May 5 11:27:52 2007 Return-Path: X-Original-To: freebsd-standards@freebsd.org Delivered-To: freebsd-standards@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D140716A401 for ; Sat, 5 May 2007 11:27:52 +0000 (UTC) (envelope-from prog@msobczak.com) Received: from mail1.fluidhosting.com (mx13.fluidhosting.com [204.14.89.3]) by mx1.freebsd.org (Postfix) with SMTP id 8CC0113C45A for ; Sat, 5 May 2007 11:27:52 +0000 (UTC) (envelope-from prog@msobczak.com) Received: (qmail 14722 invoked by uid 399); 5 May 2007 11:01:10 -0000 Received: from localhost (HELO ?192.168.1.13?) (maciej@msobczak.com@127.0.0.1) by localhost with SMTP; 5 May 2007 11:01:10 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <463C63F1.6050204@msobczak.com> Date: Sat, 05 May 2007 13:01:05 +0200 From: Maciej Sobczak User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221) MIME-Version: 1.0 To: freebsd-standards@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: Conventions for system headers 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: Sat, 05 May 2007 11:27:52 -0000 Hi (this is my first post to this list), The C99 standard defines the following requirement (7.1.2/4): "Standard headers may be included in any order [...]" This provides guarantees for language users, but at the same time imposes restrictions on language implementers on how the headers should be written themselves. The rationale for this paragraph is that headers which are insensitive to their order of inclusion ease the maintenance of user code and allow arbitrary conventions related to the use of #include directives (like, say, include in lexicographical order, etc.). What's important here is that this guarantee relates formally to 24 Standard C headers, enumerated in 7.1.2/2. In FreeBSD these headers are conveniently put in the /usr/include directory. The problem is that the same directory contains many other headers. Formally, the guarantee from 7.1.2/4 does not relate to those other headers, since they are not Standard C. But at the same time the rationale that stands behind this paragraph is reasonable enough that it could be extended to all system headers. An important potential gain is the ease of porting of software written with other POSIX-compliant systems in mind, where by chance system headers are not sensitive to their inclusion order. Currently such software might not compile on FreeBSD only due to the sensitivity of FreeBSD's headers - whether the ordering of #include directive in the software matches that required on FreeBSD is a matter of luck. I would like to propose a campaign of bringing all FreeBSD system headers in line with the guarantee that C99 provides for its standard headers, for the benefit and convenience of both developers and port maintainers. I'm aware of the fact that doing this requires some involvement, but at the same time the necessary modifications are relatively simple. Please note that a "standard" test for compliance with 7.1.2/4 is either the following test source that can be applied (even automatically) for any header X.h: /* X_test.h */ #include #include /* eof */ or, without testing the sensitivity to multiple inclusion, just: $ gcc -c -x c X.h -o /dev/null Regards, -- Maciej Sobczak : http://www.msobczak.com/ Programming : http://www.msobczak.com/prog/