mirror of
https://github.com/reactos/reactos.git
synced 2025-06-06 01:40:36 +00:00
Compilers other than GCC deserve offsetof, don't they?
svn path=/trunk/; revision=41519
This commit is contained in:
parent
d38eca89a3
commit
da2965ea12
1 changed files with 5 additions and 1 deletions
|
@ -287,7 +287,7 @@ typedef long ssize_t;
|
|||
symbols in the _FOO_T_ family, stays defined even after its
|
||||
corresponding type is defined). If we define wchar_t, then we
|
||||
must undef _WCHAR_T_; for BSD/386 1.1 (and perhaps others), if
|
||||
we undef _WCHAR_T_, then we must also define rune_t, since
|
||||
we undef _WCHAR_T_, then we must also define rune_t, since
|
||||
headers like runetype.h assume that if machine/ansi.h is included,
|
||||
and _BSD_WCHAR_T_ is not defined, then rune_t is available.
|
||||
machine/ansi.h says, "Note that _WCHAR_T_ and _RUNE_T_ must be of
|
||||
|
@ -390,7 +390,11 @@ typedef __WCHAR_TYPE__ wchar_t;
|
|||
#ifndef offsetof
|
||||
|
||||
/* Offset of member MEMBER in a struct of type TYPE. */
|
||||
#if defined(__GNUC__)
|
||||
#define offsetof(TYPE, MEMBER) __builtin_offsetof (TYPE, MEMBER)
|
||||
#else
|
||||
#define offsetof(TYPE, MEMBER) ((size_t)&(((TYPE *)0)->MEMBER))
|
||||
#endif
|
||||
|
||||
#endif /* !offsetof */
|
||||
|
||||
|
|
Loading…
Reference in a new issue