7eef194a93
To make it match what the compiler expects. on nuttx-ci-linux image: root@fec5a6192c70:/tools# gcc -dM -E - < /dev/null | grep -E "UINT(32|64)_TYPE" #define __UINT64_TYPE__ long unsigned int #define __UINT32_TYPE__ unsigned int root@fec5a6192c70:/tools# on macOS: spacetanuki% x86_64-elf-gcc -dM -E - < /dev/null | grep -E "UINT(32|64)_TYPE" #define __UINT32_TYPE__ unsigned int #define __UINT64_TYPE__ long unsigned int spacetanuki% |
||
---|---|---|
.. | ||
intel64 | ||
.gitignore | ||
arch.h | ||
inttypes.h | ||
io.h | ||
irq.h | ||
limits.h | ||
multiboot2.h | ||
README.txt | ||
syscall.h | ||
tls.h | ||
types.h |
arch/x86_64/include/README.txt ^^^^^^^^^^^^^^^^^^^^^^^^^^^ This directory holds x86_64-specific header files. The top-level header files in arch/x86_64/include simply include corresponding header files from lower lower- level chip-specific and architecture-specific directories. Architecture-Specific Directories ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Architecture-specific directories hold common header files for specific x86_64 architectures. intel64 This directory holds definitions appropriate for any instantiation of the Intel architecture in 64bit long mode. Chip-Specific directories ^^^^^^^^^^^^^^^^^^^^^^^^^ The same x86 architecture may be realized in different chip implementations. For SoC chips, in particular, on-chip devices and differing interrupt structures may require special, chip-specific definitions in these chip- specific directories. broadwell This is the implementation of NuttX on the Intel Broadwell processors.