Practical Use of Zero-Length Bitfields

by

You use a zero-length bitfield as a hacky way to get your compiler to lay out a structure to match some external requirement, be it another compiler’s or architecture’s notion of the layout (cross-platform data structures, such as in a binary file format) or a bit-level standard’s requirements (network packets or instruction opcodes).

A real-world example is when NeXT ported the xnu kernel from the Motorola 68000 (m68k) architecture to the i386 architecture. NeXT had a working m68k version of their kernel. When they ported it to i386, they found that the i386’s alignment requirements differed from the m68k’s in such a way that an m68k machine and an i386 machine did not agree on the layout of the NeXT vendor-specific BOOTP structure. In order to make the i386 structure layout agree with the m68k, they added an unnamed bitfield of length zero to force the NV1 structure/nv_U union to be 16-bit aligned.

Here are the relevant parts from the Mac OS X 10.6.5 xnu source code:

/* from xnu/bsd/netinet/bootp.h */
/*
 * Bootstrap Protocol (BOOTP).  RFC 951.
 */
/*
 * HISTORY
 *
 * 14 May 1992 ? at NeXT
 *  Added correct padding to struct nextvend.  This is
 *  needed for the i386 due to alignment differences wrt
 *  the m68k.  Also adjusted the size of the array fields
 *  because the NeXT vendor area was overflowing the bootp
 *  packet.
 */
/* . . . */
struct nextvend {
  u_char nv_magic[4]; /* Magic number for vendor specificity */
  u_char nv_version;  /* NeXT protocol version */
  /*
   * Round the beginning
   * of the union to a 16
   * bit boundary due to
   * struct/union alignment
   * on the m68k.
   */
  unsigned short  :0;
  union {
    u_char NV0[58];
    struct {
      u_char NV1_opcode;  /* opcode - Version 1 */
      u_char NV1_xid; /* transcation id */
      u_char NV1_text[NVMAXTEXT]; /* text */
      u_char NV1_null;  /* null terminator */
    } NV1;
  } nv_U;
};

More Related Contents:

  1. What does a colon in a struct declaration mean, such as :1, :7, :16, or :32?
  2. What does ‘unsigned temp:3’ in a struct or union mean? [duplicate]
  3. Is it safe to use -1 to set all bits to true?
  4. When is it worthwhile to use bit fields?
  5. What is the difference between palindrome permutation and permutation? [closed]
  6. How do you set, clear, and toggle a single bit?
  7. How do you serialize an object in C++?
  8. How to find the index of current object in range-based for loop?
  9. Is the safe-bool idiom obsolete in C++11?
  10. How to cin Space in c++?
  11. Is calling destructor manually always a sign of bad design?
  12. Efficient way of reading a file into an std::vector?
  13. calling destructor explicitly
  14. Labels in GCC inline assembly
  15. Is auto as a parameter in a regular function a GCC 4.9 extension?
  16. tell cin to stop reading at newline
  17. Declaring multiple object pointers on one line causes compiler error
  18. What is a symbol table?
  19. Create an Application without a Window
  20. Comparing strings lexicographically
  21. Easy way find uninitialized member variables
  22. Unresolved external symbol LNK2019
  23. Why can a T* be passed in register, but a unique_ptr cannot?
  24. How to enable C++17 support in VSCode C++ Extension
  25. Vector.erase(Iterator) causes bad memory access
  26. Why and how should I use namespaces in C++?
  27. Loading a file into a vector
  28. C++11 memory_order_acquire and memory_order_release semantics?
  29. How to implement “_mm_storeu_epi64” without aliasing problems?
  30. What is a reference-to-pointer?

Leave a Comment