Commit ab9afc09 by Andris Pavenis Committed by Andris Pavenis

Update typedefs for integer types in config/i386/djgpp-stdint.h

	* config/i386/djgpp-stdint.h: update typedefs for integer types

From-SVN: r231804
parent 5a6c8ffa
2015-12-18 Andris Pavenis <andris.pavenis@iki.fi>
* config/i386/djgpp-stdint.h: update typedefs for integer types
2015-12-17 Jeff Law <law@redhat.com>
* passes.def: Put the split-paths pass immediately before the
......@@ -22,21 +22,21 @@ along with GCC; see the file COPYING3. If not see
/* Exact-width integer types */
#define INT8_TYPE "signed char"
#define INT16_TYPE "signed short int"
#define INT32_TYPE "signed long int"
#define INT64_TYPE "signed long long int"
#define INT16_TYPE "short int"
#define INT32_TYPE "int"
#define INT64_TYPE "long long int"
#define UINT8_TYPE "unsigned char"
#define UINT16_TYPE "short unsigned int"
#define UINT32_TYPE "long unsigned int"
#define UINT32_TYPE "unsigned int"
#define UINT64_TYPE "long long unsigned int"
/* Minimum-width integer types */
#define INT_LEAST8_TYPE "signed char"
#define INT_LEAST16_TYPE "signed short int"
#define INT_LEAST32_TYPE "signed int"
#define INT_LEAST64_TYPE "signed long long int"
#define INT_LEAST16_TYPE "short int"
#define INT_LEAST32_TYPE "int"
#define INT_LEAST64_TYPE "long long int"
#define UINT_LEAST8_TYPE "unsigned char"
#define UINT_LEAST16_TYPE "short unsigned int"
......@@ -46,12 +46,12 @@ along with GCC; see the file COPYING3. If not see
/* Fastest minimum-width integer types */
#define INT_FAST8_TYPE "signed char"
#define INT_FAST16_TYPE "signed int"
#define INT_FAST32_TYPE "signed int"
#define INT_FAST64_TYPE "long long signed int"
#define INT_FAST16_TYPE "short int"
#define INT_FAST32_TYPE "int"
#define INT_FAST64_TYPE "long long int"
#define UINT_FAST8_TYPE "unsigned char"
#define UINT_FAST16_TYPE "unsigned int"
#define UINT_FAST16_TYPE "short unsigned int"
#define UINT_FAST32_TYPE "unsigned int"
#define UINT_FAST64_TYPE "long long unsigned int"
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment