milieu.h revision 1.2
1/* $NetBSD: milieu.h,v 1.2 2003/04/22 15:10:04 christos Exp $ */ 2 3/* This is a derivative work. */ 4 5/*- 6 * Copyright (c) 2001 The NetBSD Foundation, Inc. 7 * All rights reserved. 8 * 9 * This code is derived from software contributed to The NetBSD Foundation 10 * by Ross Harvey. 11 * 12 * Redistribution and use in source and binary forms, with or without 13 * modification, are permitted provided that the following conditions 14 * are met: 15 * 1. Redistributions of source code must retain the above copyright 16 * notice, this list of conditions and the following disclaimer. 17 * 2. Redistributions in binary form must reproduce the above copyright 18 * notice, this list of conditions and the following disclaimer in the 19 * documentation and/or other materials provided with the distribution. 20 * 3. All advertising materials mentioning features or use of this software 21 * must display the following acknowledgement: 22 * This product includes software developed by the NetBSD 23 * Foundation, Inc. and its contributors. 24 * 4. Neither the name of The NetBSD Foundation nor the names of its 25 * contributors may be used to endorse or promote products derived 26 * from this software without specific prior written permission. 27 * 28 * THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS 29 * ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED 30 * TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 31 * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS 32 * BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 33 * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 34 * SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 35 * INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 36 * CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 37 * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 38 * POSSIBILITY OF SUCH DAMAGE. 39 */ 40 41/* 42=============================================================================== 43 44This C header file is part of TestFloat, Release 2a, a package of programs 45for testing the correctness of floating-point arithmetic complying to the 46IEC/IEEE Standard for Floating-Point. 47 48Written by John R. Hauser. More information is available through the Web 49page `http://HTTP.CS.Berkeley.EDU/~jhauser/arithmetic/TestFloat.html'. 50 51THIS SOFTWARE IS DISTRIBUTED AS IS, FOR FREE. Although reasonable effort 52has been made to avoid it, THIS SOFTWARE MAY CONTAIN FAULTS THAT WILL AT 53TIMES RESULT IN INCORRECT BEHAVIOR. USE OF THIS SOFTWARE IS RESTRICTED TO 54PERSONS AND ORGANIZATIONS WHO CAN AND WILL TAKE FULL RESPONSIBILITY FOR ANY 55AND ALL LOSSES, COSTS, OR OTHER PROBLEMS ARISING FROM ITS USE. 56 57Derivative works are acceptable, even for commercial purposes, so long as 58(1) they include prominent notice that the work is derivative, and (2) they 59include prominent notice akin to these four paragraphs for those parts of 60this code that are retained. 61 62=============================================================================== 63*/ 64 65#ifndef MILIEU_H 66#define MILIEU_H 67 68#if !defined(_KERNEL) && !defined(_STANDALONE) 69#include <inttypes.h> 70#else 71#include <sys/inttypes.h> 72#endif 73 74#include <sys/endian.h> 75 76/* 77------------------------------------------------------------------------------- 78One of the macros `BIGENDIAN' or `LITTLEENDIAN' must be defined. 79------------------------------------------------------------------------------- 80*/ 81 82#if _BYTE_ORDER == _LITTLE_ENDIAN 83#define LITTLEENDIAN 84#else 85#define BIGENDIAN 86#endif 87 88#define BITS64 89 90/* 91------------------------------------------------------------------------------- 92Each of the following `typedef's defines the most convenient type that holds 93integers of at least as many bits as specified. For example, `uint8' should 94be the most convenient type that can hold unsigned integers of as many as 958 bits. The `flag' type must be able to hold either a 0 or 1. For most 96implementations of C, `flag', `uint8', and `int8' should all be `typedef'ed 97to the same as `int'. 98------------------------------------------------------------------------------- 99*/ 100typedef int flag; 101typedef unsigned int uint8; 102typedef signed int int8; 103typedef unsigned int uint16; 104typedef int int16; 105typedef unsigned int uint32; 106typedef signed int int32; 107#ifdef BITS64 108typedef uint64_t uint64; 109typedef int64_t int64; 110#endif 111 112/* 113------------------------------------------------------------------------------- 114Each of the following `typedef's defines a type that holds integers 115of _exactly_ the number of bits specified. For instance, for most 116implementation of C, `bits16' and `sbits16' should be `typedef'ed to 117`unsigned short int' and `signed short int' (or `short int'), respectively. 118------------------------------------------------------------------------------- 119*/ 120typedef uint8_t bits8; 121typedef int8_t sbits8; 122typedef uint16_t bits16; 123typedef int16_t sbits16; 124typedef uint32_t bits32; 125typedef int32_t sbits32; 126#ifdef BITS64 127typedef uint64_t bits64; 128typedef int64_t sbits64; 129#endif 130 131#ifdef BITS64 132/* 133------------------------------------------------------------------------------- 134The `LIT64' macro takes as its argument a textual integer literal and 135if necessary ``marks'' the literal as having a 64-bit integer type. 136For example, the GNU C Compiler (`gcc') requires that 64-bit literals be 137appended with the letters `LL' standing for `long long', which is `gcc's 138name for the 64-bit integer type. Some compilers may allow `LIT64' to be 139defined as the identity macro: `#define LIT64( a ) a'. 140------------------------------------------------------------------------------- 141*/ 142#define LIT64( a ) a##LL 143#endif 144 145/* 146------------------------------------------------------------------------------- 147The macro `INLINE' can be used before functions that should be inlined. If 148a compiler does not support explicit inlining, this macro should be defined 149to be `static'. 150------------------------------------------------------------------------------- 151*/ 152#define INLINE static inline 153 154#endif 155