[lwip-devel] [bug #33485] SOCK_ADDR_TYPE_MATCH and SOCK_ADDR_TYPE_MATCH_OR_UNSPEC use error

[Bill Auerbach]

Follow-up Comment #6, bug #33485 (project lwip):

>From the draft C99 standard (6.7.2.1), you'll note the compiler can add any
padding is chooses between members.  So the alignment1 and alignment2 are also
second guessing the compiler, aren't they?

12 Each non-bit-field member of a structure or union object is aligned in an
implementationdefined
manner appropriate to its type.

13 Within a structure object, the non-bit-field members and the units in which
bit-fields reside have addresses that increase in the order in which they are
declared. A pointer to a structure object, suitably converted, points to its
initial member (or if that member is a bit-field, then to the unit in which it
resides), and vice versa. There may be unnamed padding within a structure
object, but not at its beginning.

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?33485>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/