Remove ambiguity from e_flags definition #112

Open
opened 4 years ago by wschmidt-ibm · 0 comments
wschmidt-ibm commented 4 years ago (Migrated from github.com)

The bottom two bits of e_flags are used to identify the ELF ABI level. These are an encoding such that 00 = unspecified, 01 = ELFv1, 10 = ELFv2, and 11 = reserved. The current language makes it easy to believe that these are flag bits, with bit 0 unspecified, bit 1 is ELFv1, and bit 2 is ELFv2. Clarify the language.

The bottom two bits of e_flags are used to identify the ELF ABI level. These are an encoding such that 00 = unspecified, 01 = ELFv1, 10 = ELFv2, and 11 = reserved. The current language makes it easy to believe that these are flag bits, with bit 0 unspecified, bit 1 is ELFv1, and bit 2 is ELFv2. Clarify the language.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: systemsoftware/ELFv2-ABI#112
Loading…
There is no content yet.