[Pkg-chromium-maint] Bug#660187: chromium-browser: Entry #3 in data pack points off end of file. Was the file corrupted?

Jonathan Nieder jrnieder at gmail.com
Wed Jun 13 06:44:04 UTC 2012

shawn wrote:

>                                             And why do a copy when you
> don't have to? 

It's how you perform an unaligned access in C.  The copy is optimized
away on platforms that allow that.

If the question is "why rename the data member", the answer is that
that prevents new unaligned accesses from being introduced without
anyone noticing.

If the question is "why not use memcmp()", the answer is that memcmp
does a big-endian comparison but the expected semantics here are

Hope that helps,

More information about the Pkg-chromium-maint mailing list