From owner-freebsd-standards@FreeBSD.ORG Sun Dec 21 13:47:21 2003 Return-Path: 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 AA7C216A4CE for ; Sun, 21 Dec 2003 13:47:21 -0800 (PST) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA8A143D5D for ; Sun, 21 Dec 2003 13:47:16 -0800 (PST) (envelope-from kargl@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) hBLLlG5x028044 for ; Sun, 21 Dec 2003 13:47:16 -0800 (PST) (envelope-from kargl@troutmask.apl.washington.edu) Received: (from kargl@localhost)hBLLlGrr028043 for freebsd-standards@freebsd.org; Sun, 21 Dec 2003 13:47:16 -0800 (PST) (envelope-from kargl) From: "Steven G. Kargl" Message-Id: <200312212147.hBLLlGrr028043@troutmask.apl.washington.edu> To: freebsd-standards@freebsd.org Date: Sun, 21 Dec 2003 13:47:16 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Subject: fenv.h implementation questions X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Dec 2003 21:47:21 -0000 Is the following a sufficient implementation of fenv.h? _fenv_t and _fexcept_t would be defined in machine/fenv.h, which I haven't implemented, yet. I'm assuming that these may be architecture specific (e.g., endianness). SuSv3 states that the exception and rounding mode macros are to be defined *if and only if* the implementation supports them. It also states that the function prototypes that I've include need to be specified. However, why would we need to specify, say, fegetround(), if the implementation doesn't support control of the rounding mode? Finally, how the heck do we implement the #pragma at the end? #ifndef _FENV_H_ #define _FENV_H_ #include #include typedef fenv_t _fenv_t; typedef fexcept_t _fexcept_t; #ifdef _EXCEPTIONS #define FE_DIVBYZERO 0x00000001 /* Divide by zero */ #define FE_INEXACT 0x00000002 /* Inexact flag raised */ #define FE_INVALID 0x00000004 /* Invalid operation */ #define FE_OVERFLOW 0x00000008 /* Overflow */ #define FE_UNDERFLOW 0x00000010 /* Underflow */ #define FE_ALL_EXCEPT 0x0000001F /* Bitwise-or of above flags */ #endif /* _EXCEPTIONS */ #ifdef _ROUNDING_MODES #define FE_DOWNWARD 0x00000020 /* Round downward */ #define FE_TONEAREST 0x00000040 /* Round to nearest */ #define FE_TOWARDZERO 0x00000080 /* Round towards zero */ #define FE_UPWARD 0x00000100 /* Round upwards */ #endif /* _ROUNDING_MODES */ #define FE_DFL_ENV (fenv_t const *) #if !defined(_FENV_INLINED_) __BEGIN_DECLS extern int feclearexcept(int); extern int fegetenv(fenv_t *); extern int fegetexceptflag(fexcept_t *, int); extern int fegetround(void); extern int feholdexcept(fenv_t *); extern int feraiseexcept(int); extern int fesetenv(const fenv_t *); extern int fesetexceptflag(const fexcept_t *, int); extern int fesetround(int); extern int fetestexcept(int); extern int feupdateenv(fenv_t *); __END_DECLS #endif /* !_FENV_INLINED_ */ #if 0 /* XXX Need to implement the FENV_ACCESS pragma */ #endif #endif /* _FENV_H_ */ -- Steve http://troutmask.apl.washington.edu/~kargl/ From owner-freebsd-standards@FreeBSD.ORG Sun Dec 21 23:47:11 2003 Return-Path: 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 D002316A4CE for ; Sun, 21 Dec 2003 23:47:11 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB2E443D55 for ; Sun, 21 Dec 2003 23:47:05 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3p2/8.8.7) with ESMTP id SAA15863; Mon, 22 Dec 2003 18:46:59 +1100 Date: Mon, 22 Dec 2003 18:46:58 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: "Steven G. Kargl" In-Reply-To: <200312212147.hBLLlGrr028043@troutmask.apl.washington.edu> Message-ID: <20031222182536.C7679@gamplex.bde.org> References: <200312212147.hBLLlGrr028043@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-standards@freebsd.org Subject: Re: fenv.h implementation questions X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Dec 2003 07:47:12 -0000 On Sun, 21 Dec 2003, Steven G. Kargl wrote: > Is the following a sufficient implementation of fenv.h? > _fenv_t and _fexcept_t would be defined in machine/fenv.h, > which I haven't implemented, yet. I'm assuming that > these may be architecture specific (e.g., endianness). fenv_t and fexcept_t are very MD, and hopefully aren't needed in more than 1 file, so they should be declared directly in . > SuSv3 states that the exception and rounding mode macros > are to be defined *if and only if* the implementation > supports them. It also states that the function prototypes > that I've include need to be specified. However, why would > we need to specify, say, fegetround(), if the implementation > doesn't support control of the rounding mode? C99 says the same. I guess it is not expected that all rounding modes are unsupported (after all, there should be a default rounding mode and even if it is weird than it could be described by a nonstandard FE_ macro). fegetround() is needed if more than 2 rounding modes are supported and useful for avoiding special cases if only 1 rounding mode is supported. It is only not useful if no rounding mode is supported (since then it should not be called since it has no valid arg). > Finally, how the heck do we implement the #pragma at the end? Finish the relevant part of the C99 support in gcc, or wait for it. I think this is a large task. It would involve turning off certain optimizations within the FENV_ACCESS ON region. > #ifndef _FENV_H_ > #define _FENV_H_ > > #include > #include > > typedef fenv_t _fenv_t; > typedef fexcept_t _fexcept_t; > > #ifdef _EXCEPTIONS > #define FE_DIVBYZERO 0x00000001 /* Divide by zero */ > #define FE_INEXACT 0x00000002 /* Inexact flag raised */ > #define FE_INVALID 0x00000004 /* Invalid operation */ > #define FE_OVERFLOW 0x00000008 /* Overflow */ > #define FE_UNDERFLOW 0x00000010 /* Underflow */ > #define FE_ALL_EXCEPT 0x0000001F /* Bitwise-or of above flags */ > #endif /* _EXCEPTIONS */ > > #ifdef _ROUNDING_MODES > #define FE_DOWNWARD 0x00000020 /* Round downward */ > #define FE_TONEAREST 0x00000040 /* Round to nearest */ > #define FE_TOWARDZERO 0x00000080 /* Round towards zero */ > #define FE_UPWARD 0x00000100 /* Round upwards */ > #endif /* _ROUNDING_MODES */ These should probably all be MD. It saves a negative amount of code to use a common definition since larger code would be required to convert between the MI bits and the MI bits. > > #define FE_DFL_ENV (fenv_t const *) This needs to point to something. > > #if !defined(_FENV_INLINED_) > __BEGIN_DECLS > extern int feclearexcept(int); > extern int fegetenv(fenv_t *); > extern int fegetexceptflag(fexcept_t *, int); > extern int fegetround(void); > extern int feholdexcept(fenv_t *); > extern int feraiseexcept(int); > extern int fesetenv(const fenv_t *); > extern int fesetexceptflag(const fexcept_t *, int); > extern int fesetround(int); > extern int fetestexcept(int); > extern int feupdateenv(fenv_t *); > __END_DECLS > #endif /* !_FENV_INLINED_ */ I don't see much point in inlining these (like the i386 fp* versions). Marcel pointed out that inline versions are good for backwards compatibility (the library can be changed without affecting old interfaces), but we don't need that for standard interfaces. > > #if 0 > /* XXX Need to implement the FENV_ACCESS pragma */ > #endif > > #endif /* _FENV_H_ */ Bruce From owner-freebsd-standards@FreeBSD.ORG Mon Dec 22 11:03:13 2003 Return-Path: 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 03A2116A4CE for ; Mon, 22 Dec 2003 11:03:13 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C36F543D9E for ; Mon, 22 Dec 2003 11:01:45 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) hBMJ1VFR067476 for ; Mon, 22 Dec 2003 11:01:31 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id hBMJ1U2H067470 for freebsd-standards@freebsd.org; Mon, 22 Dec 2003 11:01:30 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 22 Dec 2003 11:01:30 -0800 (PST) Message-Id: <200312221901.hBMJ1U2H067470@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 Subject: Current problem reports assigned to you X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Dec 2003 19:03:13 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- s [2001/01/23] misc/24590 standards timezone function not compatible witn Sin o [2002/02/25] bin/35307 standards standard include files are not standard c o [2003/03/05] bin/48958 standards The type 'bool' has different sizes for C o [2003/04/21] standards/51209standards [PATCH] add a64l()/l64a/l64a_r functions p [2003/06/05] standards/52972standards /bin/sh arithmetic not POSIX compliant o [2003/06/20] standards/53554standards interval timers not cleared in fork() o [2003/07/12] standards/54410standards one-true-awk not POSIX compliant (no exte o [2003/09/15] standards/56906standards Several math(3) functions fail to set err 8 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/01/16] bin/24390 standards Replacing old dir-symlinks when using /bi o [2001/11/20] standards/32126standards getopt(3) not Unix-98 conformant s [2002/03/18] standards/36076standards Implementation of POSIX fuser command o [2002/06/13] standards/39256standards [v]snprintf aren't POSIX-conformant for s o [2002/07/09] misc/40378 standards stdlib.h gives needless warnings with -an 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 [2002/12/23] standards/46504standards Warnings in headers o [2003/04/22] standards/51292standards [PATCH] add ecvt()/fcvt()/gcvt() function o [2003/06/22] standards/53613standards FreeBSD doesn't define EPROTO o [2003/06/24] bin/53682 standards [PATCH] add fuser(1) utitity o [2003/07/24] standards/54809standards pcvt deficits o [2003/07/24] 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/04] standards/56476standards cd9660 unicode support simple hack o [2003/09/27] standards/57295standards [patch] make does not include cmd line va o [2003/10/12] standards/57911standards fnmatch ("[[:alpha:]]","x", FNM_PATHNAME) o [2003/10/29] standards/58676standards grantpt(3) alters storage used by ptsname o [2003/11/29] standards/59797standards Implement C99's round[f]() math fucntions 21 problems total. From owner-freebsd-standards@FreeBSD.ORG Mon Dec 22 11:05:40 2003 Return-Path: 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 4853E16A4D0 for ; Mon, 22 Dec 2003 11:05:40 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2D5943D5C for ; Mon, 22 Dec 2003 11:04:41 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.10/8.12.10) with ESMTP id hBMJ3FFR069577 for ; Mon, 22 Dec 2003 11:03:15 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id hBMJ3E0V069571 for standards@freebsd.org; Mon, 22 Dec 2003 11:03:14 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 22 Dec 2003 11:03:14 -0800 (PST) Message-Id: <200312221903.hBMJ3E0V069571@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: standards@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Dec 2003 19:05:40 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/08/18] kern/29844 standards [PATCH] setpgrp does not behave as manual 1 problem total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/03/05] bin/25542 standards /bin/sh: null char in quoted string 1 problem total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- f [1995/01/11] i386/105 standards Distributed libm (msun) has non-standard o [2000/09/24] bin/21519 standards sys/dir.h should be deprecated some more o [2000/12/05] kern/23304 standards POSIX clock_gettime, clock_getres return s [2001/06/18] kern/28260 standards UIO_MAXIOV needs to be made public 4 problems total. From owner-freebsd-standards@FreeBSD.ORG Tue Dec 23 22:00:09 2003 Return-Path: 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 A82A916A4CF for ; Tue, 23 Dec 2003 22:00:09 -0800 (PST) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6093443D49 for ; Tue, 23 Dec 2003 22:00:07 -0800 (PST) (envelope-from kargl@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) hBO6065x066757; Tue, 23 Dec 2003 22:00:06 -0800 (PST) (envelope-from kargl@troutmask.apl.washington.edu) Received: (from kargl@localhost)hBO606TJ066756; Tue, 23 Dec 2003 22:00:06 -0800 (PST) (envelope-from kargl) From: "Steven G. Kargl" Message-Id: <200312240600.hBO606TJ066756@troutmask.apl.washington.edu> In-Reply-To: <20031222182536.C7679@gamplex.bde.org> To: Bruce Evans Date: Tue, 23 Dec 2003 22:00:06 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII cc: freebsd-standards@freebsd.org Subject: Re: fenv.h implementation questions X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Dec 2003 06:00:09 -0000 Bruce Evans wrote: > On Sun, 21 Dec 2003, Steven G. Kargl wrote: > > > Is the following a sufficient implementation of fenv.h? > > _fenv_t and _fexcept_t would be defined in machine/fenv.h, > > which I haven't implemented, yet. I'm assuming that > > these may be architecture specific (e.g., endianness). > > fenv_t and fexcept_t are very MD, and hopefully aren't needed > in more than 1 file, so they should be declared directly in > . Certainly, fenv_t and fexcept_t are MD, but I don't believe that their use is restricted to 1 file (unless I'm totally misinterpreting what you wrote). Consider, #include #include #include int foo(x) { double x; fexcept_t bar; errno = 0; x = ceil(x); if (errno != 0) { /* FE occurred */ fegetexception(&bar, FE_ALL_EXCEPT); /* Do something to address FE */ } else { .... } } (snip) > > #ifdef _EXCEPTIONS > > #define FE_DIVBYZERO 0x00000001 /* Divide by zero */ > > #define FE_INEXACT 0x00000002 /* Inexact flag raised */ > > #define FE_INVALID 0x00000004 /* Invalid operation */ > > #define FE_OVERFLOW 0x00000008 /* Overflow */ > > #define FE_UNDERFLOW 0x00000010 /* Underflow */ > > #define FE_ALL_EXCEPT 0x0000001F /* Bitwise-or of above flags */ > > #endif /* _EXCEPTIONS */ > > > > #ifdef _ROUNDING_MODES > > #define FE_DOWNWARD 0x00000020 /* Round downward */ > > #define FE_TONEAREST 0x00000040 /* Round to nearest */ > > #define FE_TOWARDZERO 0x00000080 /* Round towards zero */ > > #define FE_UPWARD 0x00000100 /* Round upwards */ > > #endif /* _ROUNDING_MODES */ > > These should probably all be MD. It saves a negative amount of code to > use a common definition since larger code would be required to convert > between the MI bits and the MI bits. > I'll have to look at SuSv3 again, but the above definitions should be suitable for both big and little endian machines. I'm not sure about 32 bit versus 64 bit machines. Are you concerned that an architecture may only support a subset of the above flags? -- Steve http://troutmask.apl.washington.edu/~kargl/ From owner-freebsd-standards@FreeBSD.ORG Wed Dec 24 01:09:47 2003 Return-Path: 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 0E53616A4CE for ; Wed, 24 Dec 2003 01:09:47 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A8B043D1F for ; Wed, 24 Dec 2003 01:09:45 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3p2/8.8.7) with ESMTP id UAA13147; Wed, 24 Dec 2003 20:09:39 +1100 Date: Wed, 24 Dec 2003 20:09:39 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: "Steven G. Kargl" In-Reply-To: <200312240600.hBO606TJ066756@troutmask.apl.washington.edu> Message-ID: <20031224200114.F5421@gamplex.bde.org> References: <200312240600.hBO606TJ066756@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-standards@freebsd.org Subject: Re: fenv.h implementation questions X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Dec 2003 09:09:47 -0000 On Tue, 23 Dec 2003, Steven G. Kargl wrote: > Bruce Evans wrote: > > On Sun, 21 Dec 2003, Steven G. Kargl wrote: > > > > > Is the following a sufficient implementation of fenv.h? > > > _fenv_t and _fexcept_t would be defined in machine/fenv.h, > > > which I haven't implemented, yet. I'm assuming that > > > these may be architecture specific (e.g., endianness). > > > > fenv_t and fexcept_t are very MD, and hopefully aren't needed > > in more than 1 file, so they should be declared directly in > > . > > Certainly, fenv_t and fexcept_t are MD, but I don't > believe that their use is restricted to 1 file (unless > I'm totally misinterpreting what you wrote). Consider, I checked. It is only defined in according to C99 (n869.txt draft) and and POSIX.1-2001 (draft7). > #include > #include > #include > > int foo(x) { > double x; > fexcept_t bar; > errno = 0; > x = ceil(x); > if (errno != 0) { /* FE occurred */ > fegetexception(&bar, FE_ALL_EXCEPT); > /* Do something to address FE */ > } else { > .... > } > } You got it from there. It is not in though. > (snip) > > > > #ifdef _EXCEPTIONS > > > #define FE_DIVBYZERO 0x00000001 /* Divide by zero */ > > > #define FE_INEXACT 0x00000002 /* Inexact flag raised */ > > > #define FE_INVALID 0x00000004 /* Invalid operation */ > > > #define FE_OVERFLOW 0x00000008 /* Overflow */ > > > #define FE_UNDERFLOW 0x00000010 /* Underflow */ > > > #define FE_ALL_EXCEPT 0x0000001F /* Bitwise-or of above flags */ > > > #endif /* _EXCEPTIONS */ > > > > > > #ifdef _ROUNDING_MODES > > > #define FE_DOWNWARD 0x00000020 /* Round downward */ > > > #define FE_TONEAREST 0x00000040 /* Round to nearest */ > > > #define FE_TOWARDZERO 0x00000080 /* Round towards zero */ > > > #define FE_UPWARD 0x00000100 /* Round upwards */ > > > #endif /* _ROUNDING_MODES */ > > > > These should probably all be MD. It saves a negative amount of code to > > use a common definition since larger code would be required to convert > > between the MI bits and the MI bits. > > > > I'll have to look at SuSv3 again, but the above definitions > should be suitable for both big and little endian machines. > I'm not sure about 32 bit versus 64 bit machines. Are you > concerned that an architecture may only support a subset of > the above flags? Each arch has its own natural definitions of the flags. E.g., on i386's the natural division by 0 flag is FP_X_DZ = 0x04, not 0x00000001. Bruce From owner-freebsd-standards@FreeBSD.ORG Wed Dec 24 09:25:31 2003 Return-Path: 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 704C616A4CE; Wed, 24 Dec 2003 09:25:31 -0800 (PST) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E0E043D3F; Wed, 24 Dec 2003 09:25:30 -0800 (PST) (envelope-from rodrigc@crodrigues.org) Received: from h00609772adf0.ne.client2.attbi.com ([66.31.45.197]) by comcast.net (rwcrmhc12) with ESMTP id <20031224172530014000t1aee>; Wed, 24 Dec 2003 17:25:30 +0000 Received: from h00609772adf0.ne.client2.attbi.com (localhost.crodrigues.org [127.0.0.1])hBOHPcZ3093284; Wed, 24 Dec 2003 12:25:39 -0500 (EST) (envelope-from rodrigc@h00609772adf0.ne.client2.attbi.com) Received: (from rodrigc@localhost)hBOHPckQ093283; Wed, 24 Dec 2003 12:25:38 -0500 (EST) (envelope-from rodrigc) Date: Wed, 24 Dec 2003 12:25:38 -0500 From: Craig Rodrigues To: mike@freebsd.org Message-ID: <20031224172538.GA93272@crodrigues.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i cc: alfred@freebsd.org cc: freebsd-standards@freebsd.org Subject: PR 44394, adding restrict qualifiers to socket functions X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Dec 2003 17:25:31 -0000 Hi, Can someone take a look at committing PR 44394? http://www.freebsd.org/cgi/query-pr.cgi?pr=standards/44394 Thanks. -- Craig Rodrigues http://crodrigues.org rodrigc@crodrigues.org From owner-freebsd-standards@FreeBSD.ORG Wed Dec 24 10:09:21 2003 Return-Path: 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 0386316A4CE; Wed, 24 Dec 2003 10:09:21 -0800 (PST) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A7BE43D2F; Wed, 24 Dec 2003 10:09:20 -0800 (PST) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 4BFE85C7A3; Wed, 24 Dec 2003 10:09:20 -0800 (PST) Date: Wed, 24 Dec 2003 10:09:20 -0800 From: Alfred Perlstein To: Craig Rodrigues Message-ID: <20031224180920.GG60229@elvis.mu.org> References: <20031224172538.GA93272@crodrigues.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031224172538.GA93272@crodrigues.org> User-Agent: Mutt/1.4.1i cc: freebsd-standards@freebsd.org Subject: Re: PR 44394, adding restrict qualifiers to socket functions X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Dec 2003 18:09:21 -0000 * Craig Rodrigues [031224 09:25] wrote: > Hi, > > Can someone take a look at committing PR 44394? > http://www.freebsd.org/cgi/query-pr.cgi?pr=standards/44394 About to commit it.. > > Thanks. > > -- > Craig Rodrigues > http://crodrigues.org > rodrigc@crodrigues.org -- - Alfred Perlstein - Research Engineering Development Inc. - email: bright@mu.org cell: 408-480-4684 From owner-freebsd-standards@FreeBSD.ORG Wed Dec 24 11:14:48 2003 Return-Path: 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 CD1A816A4CE; Wed, 24 Dec 2003 11:14:48 -0800 (PST) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id F423343D45; Wed, 24 Dec 2003 11:14:43 -0800 (PST) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id EBDF65C78F; Wed, 24 Dec 2003 11:14:43 -0800 (PST) Date: Wed, 24 Dec 2003 11:14:43 -0800 From: Alfred Perlstein To: Craig Rodrigues Message-ID: <20031224191443.GH60229@elvis.mu.org> References: <20031224172538.GA93272@crodrigues.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031224172538.GA93272@crodrigues.org> User-Agent: Mutt/1.4.1i cc: freebsd-standards@freebsd.org Subject: Re: PR 44394, adding restrict qualifiers to socket functions X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Dec 2003 19:14:48 -0000 * Craig Rodrigues [031224 09:25] wrote: > Hi, > > Can someone take a look at committing PR 44394? > http://www.freebsd.org/cgi/query-pr.cgi?pr=standards/44394 > > Thanks. grr, this broke things. :( try regen'ing the generated files: cd src/sys/kern ; sh makesyscalls.sh syscalls.master then build... it gets sad. > > -- > Craig Rodrigues > http://crodrigues.org > rodrigc@crodrigues.org -- - Alfred Perlstein - Research Engineering Development Inc. - email: bright@mu.org cell: 408-480-4684 From owner-freebsd-standards@FreeBSD.ORG Fri Dec 26 11:50:23 2003 Return-Path: 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 0F93316A4CE for ; Fri, 26 Dec 2003 11:50:23 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A7C643D2D for ; Fri, 26 Dec 2003 11:50:18 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) hBQJoIFR078755 for ; Fri, 26 Dec 2003 11:50:18 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id hBQJoIMT078754; Fri, 26 Dec 2003 11:50:18 -0800 (PST) (envelope-from gnats) Resent-Date: Fri, 26 Dec 2003 11:50:18 -0800 (PST) Resent-Message-Id: <200312261950.hBQJoIMT078754@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-standards@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Michal Pasternak Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1748316A4CE for ; Fri, 26 Dec 2003 11:43:47 -0800 (PST) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2413443D5C for ; Fri, 26 Dec 2003 11:43:44 -0800 (PST) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.12.10/8.12.10) with ESMTP id hBQJhhdL067948 for ; Fri, 26 Dec 2003 11:43:43 -0800 (PST) (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.12.10/8.12.10/Submit) id hBQJhhsr067947; Fri, 26 Dec 2003 11:43:43 -0800 (PST) (envelope-from nobody) Message-Id: <200312261943.hBQJhhsr067947@www.freebsd.org> Date: Fri, 26 Dec 2003 11:43:43 -0800 (PST) From: Michal Pasternak To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.0 Subject: standards/60597: FreeBSD's /usr/include lacks of cpio.h X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Dec 2003 19:50:23 -0000 >Number: 60597 >Category: standards >Synopsis: FreeBSD's /usr/include lacks of cpio.h >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-standards >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Fri Dec 26 11:50:17 PST 2003 >Closed-Date: >Last-Modified: >Originator: Michal Pasternak >Release: 4-STABLE >Organization: >Environment: FreeBSD mainframe.w.lub.pl 4.9-STABLE FreeBSD 4.9-STABLE #0: Thu Dec 25 12:02:15 CET 2003 doc@mainframe.w.lub.pl:/usr/obj/usr/src/sys/MP-UX i386 >Description: FreeBSD is missing /usr/include/cpio.h file, which is mentioned in: http://www.opengroup.org/onlinepubs/007904975/basedefs/cpio.h.html (POSIX, XRG) >How-To-Repeat: N/A >Fix: Take the file from NetBSD project: http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/include/cpio.h?rev=1.2&content-type=text/plain The file itself is very simple; it is not a problem while writing applications, that use it (everyone could include them in the application source in such case), but this should not be done this way -- this file should be in basesystem. FreeBSD already include "tar.h", which is a part of the same standard. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-standards@FreeBSD.ORG Fri Dec 26 17:42:44 2003 Return-Path: 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 708E516A4CE; Fri, 26 Dec 2003 17:42:44 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0E6F43D1D; Fri, 26 Dec 2003 17:42:43 -0800 (PST) (envelope-from tjr@FreeBSD.org) Received: from freefall.freebsd.org (tjr@localhost [127.0.0.1]) hBR1ghFR008383; Fri, 26 Dec 2003 17:42:43 -0800 (PST) (envelope-from tjr@freefall.freebsd.org) Received: (from tjr@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id hBR1ghno008379; Fri, 26 Dec 2003 17:42:43 -0800 (PST) (envelope-from tjr) Date: Fri, 26 Dec 2003 17:42:43 -0800 (PST) From: "Tim J. Robbins" Message-Id: <200312270142.hBR1ghno008379@freefall.freebsd.org> To: dotz@irc.pl, tjr@FreeBSD.org, freebsd-standards@FreeBSD.org Subject: Re: standards/60597: FreeBSD's /usr/include lacks of cpio.h X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Dec 2003 01:42:44 -0000 Synopsis: FreeBSD's /usr/include lacks of cpio.h State-Changed-From-To: open->patched State-Changed-By: tjr State-Changed-When: Fri Dec 26 17:42:23 PST 2003 State-Changed-Why: -CURRENT already has this. http://www.freebsd.org/cgi/query-pr.cgi?pr=60597