<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - compiler padding causes reply parsing to use incorrect offsets" href="https://bugs.freedesktop.org/show_bug.cgi?id=23403#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - compiler padding causes reply parsing to use incorrect offsets" href="https://bugs.freedesktop.org/show_bug.cgi?id=23403">bug 23403</a> from <a class="email" href="mailto:consume.noise@gmail.com" title="Daniel Martin <consume.noise@gmail.com>"> Daniel Martin</a> <pre>(In reply to <a href="show_bug.cgi?id=23403#c4">comment #4</a>) > I don't think it makes sense to leave protocol structs incorrectly padded > and manually compute their real size, ignoring the compiler. While using > something like __attribute__((packed)) doesn't work portably across > compilers, assuming that the padding only occurs at the *end* of the > structure (and not, for instance, right before the last field) doesn't work > portably either. I think adding the packed attribute and thereby possibly breaking it for other compilers is a minor issue then leaving it broken for all (mainly gcc). But, I don't have any experience with other compilers. What do they do if they find an unsupported attribute (warning, error, ignore it silently)?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>