Displaying 3 results from an estimated 3 matches for "file_header".
2016 Mar 03
2
[cfe-dev] [3.8 Release] Please write release notes!
...e pointer. If the pointer is to a struct that represents that layout of a
> serialized structure, consider making that struct packed; this will remove any
> implicit internal padding that the compiler might add to the struct and
> reduce its alignment requirement to 1.
>
> struct file_header {
> uint16_t magic_number;
> uint16_t format_version;
> uint16_t num_entries;
> } __attribute__((packed));
If we want to include this example, it is likely a good idea to point
out that packed and aligned can be combined, i.e. if you know that the
file_header copies are g...
2016 Feb 26
2
[3.8 Release] Please write release notes!
If you were thinking about writing a note for 3.8 but didn't get
around to it yet, this is the final reminder.
(In particular, the notes for X86 and PowerPC could use some attention.)
Thanks,
Hans
On Thu, Feb 11, 2016 at 4:16 PM, Hans Wennborg <hans at chromium.org> wrote:
> Dear lots of people,
>
> The first comments on the 3.7 release expressed surprise that there
> were
2016 Feb 12
15
[3.8 Release] Please write release notes!
Dear lots of people,
The first comments on the 3.7 release expressed surprise that there
were no changes to the X86 or ARM targets. There had of course been a
lot of hard work and many changes, but none of it was mentioned in the
release notes.
Please help make the release notes more comprehensive this time. The
notes are of course not as important as the actual code, but they do
get read, and