On Thu, 16 Jun 2011, Alexander Holler wrote: > >> I thought the compiler was not allowed to insert > >> padding if the natural alignment of the data types didn't require any. > > > > It's architecture dependent. The alignment of the structure is the maximum alignment > > of its members, so it gets to be 8 bytes if there is a 64 bit member in the struct > > on most architectures, but 4 bytes on x86. > > Hmm, sorry, but that sentence just says something about the alignment of > the structure itself and nothing about the alignment of it's members or > do I understand something wrong? We're talking about padding, not alignment. Obviously these two concepts are related, since fields with differing alignment requirements sometimes force the compiler to insert padding. But they aren't the same thing. The question is whether gcc will insert padding in a structure that doesn't need it. The kernel depends on peculiarities of gcc in many ways; basing your strategy on what the C99 spec says is not always a good idea. > For me that means that I understand that when packed(,aligned(4)) is > used, it's pretty sure, that there is no padding inbetween the members > of e.g. struct ehci_regs. But without I'm unsure, so I would avoid that. > > That aligned(4) is necessary (for ARM) is only a workaround because of > the implementation of readl(), at least that is how I understood the > discussion. But that is discussed elsewhere and don't want to take part > in that discussion (and can't). Hmmm. I won't say that ((packed,aligned(4))) is wrong. But it's not clearly necessary either. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
