systemsoftware
/
ELFv2-ABI
30
1
Fork 0
Code Issues 10 Pull Requests Projects Releases Wiki Activity

Labels Milestones

New Issue

Remove ambiguity from e_flags definition #112

Open
opened 3 years ago by wschmidt-ibm · 0 comments
wschmidt-ibm commented 3 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 Branch/Tag Specified
Branches Tags
master
v1.5
v1.5_markup
V1.4
1.2b
1.5_prd
Labels
Apply labels
Clear labels   
bug
   
duplicate
   
enhancement
   
help wanted
   
invalid
   
question
   
wontfix
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Set milestone
Clear milestone
No items
No Milestone
Projects
Set Project
Clear projects
No project
Assignees
Assign users
Clear assignees
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
Write Preview
Loading…
Cancel
Save
There is no content yet.
Delete Branch '%!s(<nil>)'

Deleting a branch is permanent. It CANNOT be undone. Continue?

No
Yes