-
-/* As of 0.6.12, the FFI can't handle 64-bit values. For now, we use
- * these munged-to-32-bits values for might-be-64-bit slots of
- * stat_wrapper as a workaround, so that at least we can still work
- * when values are small.
- *
- * FIXME: But of course we should fix the FFI so that we can use the
- * actual 64-bit values instead. In fact, we probably have by now
- * (2003-10-03) on all working platforms except MIPS and HPPA; if some
- * motivated spark would simply fix those, this hack could go away.
- * -- CSR, 2003-10-03
- *
- * Some motivated spark fixed MIPS. -- ths, 2005-10-06 */
-
-#if defined (LISP_FEATURE_LARGEFILE)
-typedef dev_t ffi_dev_t;
-typedef off_t ffi_off_t;
-#elif defined(LISP_FEATURE_MIPS)
-typedef unsigned long ffi_dev_t; /* Linux/MIPS struct stat doesn't use dev_t */
-typedef off_t ffi_off_t;
-#else
-typedef u32 ffi_dev_t; /* since Linux dev_t can be 64 bits */
-typedef u32 ffi_off_t; /* since OpenBSD 2.8 st_size is 64 bits */
-#endif
-
-/* a representation of stat(2) results which doesn't depend on CPU or OS */
-struct stat_wrapper {
- /* KLUDGE: The verbose wrapped_st_ prefixes are to protect us from
- * the C preprocessor as wielded by the fiends of OpenBSD, who do
- * things like
- * #define st_atime st_atimespec.tv_sec
- * I remember when I was young and innocent, I read about how the
- * C preprocessor isn't to be used to globally munge random
- * lowercase symbols like this, because things like this could
- * happen, and I nodded sagely. But now I know better.:-| This is
- * another entry for Dan Barlow's ongoing episodic rant about C
- * header files, I guess.. -- WHN 2001-05-10 */
- ffi_dev_t wrapped_st_dev; /* device */
- ino_t wrapped_st_ino; /* inode */
- mode_t wrapped_st_mode; /* protection */