summaryrefslogtreecommitdiffstatshomepage
path: root/trunk/src/lib/softfloat/mamesf.h
diff options
context:
space:
mode:
Diffstat (limited to 'trunk/src/lib/softfloat/mamesf.h')
-rw-r--r--trunk/src/lib/softfloat/mamesf.h66
1 files changed, 66 insertions, 0 deletions
diff --git a/trunk/src/lib/softfloat/mamesf.h b/trunk/src/lib/softfloat/mamesf.h
new file mode 100644
index 00000000000..077077ee087
--- /dev/null
+++ b/trunk/src/lib/softfloat/mamesf.h
@@ -0,0 +1,66 @@
+/*----------------------------------------------------------------------------
+| One of the macros `BIGENDIAN' or `LITTLEENDIAN' must be defined.
+*----------------------------------------------------------------------------*/
+#ifdef LSB_FIRST
+#define LITTLEENDIAN
+#else
+#define BIGENDIAN
+#endif
+
+/*----------------------------------------------------------------------------
+| The macro `BITS64' can be defined to indicate that 64-bit integer types are
+| supported by the compiler.
+*----------------------------------------------------------------------------*/
+#define BITS64
+
+/*----------------------------------------------------------------------------
+| Each of the following `typedef's defines the most convenient type that holds
+| integers of at least as many bits as specified. For example, `uint8' should
+| be the most convenient type that can hold unsigned integers of as many as
+| 8 bits. The `flag' type must be able to hold either a 0 or 1. For most
+| implementations of C, `flag', `uint8', and `int8' should all be `typedef'ed
+| to the same as `int'.
+*----------------------------------------------------------------------------*/
+#include "emu.h"
+
+typedef INT8 flag;
+typedef UINT8 uint8;
+typedef INT8 int8;
+typedef UINT16 uint16;
+typedef INT16 int16;
+typedef UINT32 uint32;
+typedef INT32 int32;
+typedef UINT64 uint64;
+typedef INT64 int64;
+
+/*----------------------------------------------------------------------------
+| Each of the following `typedef's defines a type that holds integers
+| of _exactly_ the number of bits specified. For instance, for most
+| implementation of C, `bits16' and `sbits16' should be `typedef'ed to
+| `unsigned short int' and `signed short int' (or `short int'), respectively.
+*----------------------------------------------------------------------------*/
+typedef UINT8 bits8;
+typedef INT8 sbits8;
+typedef UINT16 bits16;
+typedef INT16 sbits16;
+typedef UINT32 bits32;
+typedef INT32 sbits32;
+typedef UINT64 bits64;
+typedef INT64 sbits64;
+
+/*----------------------------------------------------------------------------
+| The `LIT64' macro takes as its argument a textual integer literal and
+| if necessary ``marks'' the literal as having a 64-bit integer type.
+| For example, the GNU C Compiler (`gcc') requires that 64-bit literals be
+| appended with the letters `LL' standing for `long long', which is `gcc's
+| name for the 64-bit integer type. Some compilers may allow `LIT64' to be
+| defined as the identity macro: `#define LIT64( a ) a'.
+*----------------------------------------------------------------------------*/
+#define LIT64( a ) a##ULL
+
+/*----------------------------------------------------------------------------
+| The macro `INLINE' can be used before functions that should be inlined. If
+| a compiler does not support explicit inlining, this macro should be defined
+| to be `static'.
+*----------------------------------------------------------------------------*/
+// MAME defines INLINE