compilers/pcc/pcc-libs-1.0.0/libsoftfloat/arch/powerpc/powerpc-gcc.h

   1 /*      $NetBSD: powerpc-gcc.h,v 1.2 2005/12/24 21:11:16 perry Exp $    */
   2
   3 /*
   4 -------------------------------------------------------------------------------
   5 One of the macros `BIGENDIAN' or `LITTLEENDIAN' must be defined.
   6 -------------------------------------------------------------------------------
   7 */
   8 #include <machine/endian.h>
   9 #if _BYTE_ORDER == _BIG_ENDIAN
  10 #define BIGENDIAN
  11 #endif
  12 #if _BYTE_ORDER == _LITTLE_ENDIAN
  13 #define LITTLEENDIAN
  14 #endif
  15
  16 /*
  17 -------------------------------------------------------------------------------
  18 The macro `BITS64' can be defined to indicate that 64-bit integer types are
  19 supported by the compiler.
  20 -------------------------------------------------------------------------------
  21 */
  22 #define BITS64
  23
  24 /*
  25 -------------------------------------------------------------------------------
  26 Each of the following `typedef's defines the most convenient type that holds
  27 integers of at least as many bits as specified.  For example, `uint8' should
  28 be the most convenient type that can hold unsigned integers of as many as
  29 8 bits.  The `flag' type must be able to hold either a 0 or 1.  For most
  30 implementations of C, `flag', `uint8', and `int8' should all be `typedef'ed
  31 to the same as `int'.
  32 -------------------------------------------------------------------------------
  33 */
  34 typedef int flag;
  35 typedef int uint8;
  36 typedef int int8;
  37 typedef int uint16;
  38 typedef int int16;
  39 typedef unsigned int uint32;
  40 typedef signed int int32;
  41 #ifdef BITS64
  42 typedef unsigned long long int uint64;
  43 typedef signed long long int int64;
  44 #endif
  45
  46 /*
  47 -------------------------------------------------------------------------------
  48 Each of the following `typedef's defines a type that holds integers
  49 of _exactly_ the number of bits specified.  For instance, for most
  50 implementation of C, `bits16' and `sbits16' should be `typedef'ed to
  51 `unsigned short int' and `signed short int' (or `short int'), respectively.
  52 -------------------------------------------------------------------------------
  53 */
  54 typedef unsigned char bits8;
  55 typedef signed char sbits8;
  56 typedef unsigned short int bits16;
  57 typedef signed short int sbits16;
  58 typedef unsigned int bits32;
  59 typedef signed int sbits32;
  60 #ifdef BITS64
  61 typedef unsigned long long int bits64;
  62 typedef signed long long int sbits64;
  63 #endif
  64
  65 #ifdef BITS64
  66 /*
  67 -------------------------------------------------------------------------------
  68 The `LIT64' macro takes as its argument a textual integer literal and
  69 if necessary ``marks'' the literal as having a 64-bit integer type.
  70 For example, the GNU C Compiler (`gcc') requires that 64-bit literals be
  71 appended with the letters `LL' standing for `long long', which is `gcc's
  72 name for the 64-bit integer type.  Some compilers may allow `LIT64' to be
  73 defined as the identity macro:  `#define LIT64( a ) a'.
  74 -------------------------------------------------------------------------------
  75 */
  76 #define LIT64( a ) a##LL
  77 #endif
  78
  79 /*
  80 -------------------------------------------------------------------------------
  81 The macro `INLINE' can be used before functions that should be inlined.  If
  82 a compiler does not support explicit inlining, this macro should be defined
  83 to be `static'.
  84 -------------------------------------------------------------------------------
  85 */
  86 #define INLINE static inline
  87
  88 #define FLOAT64_DEMANGLE(a)     (a)
  89 #define FLOAT64_MANGLE(a)       (a)