Skip to content

No version information inside binary files #5

@phkeese

Description

@phkeese

Currently, there are only the magic bytes "soil", without any version or platform-specific (e.g. word size) information.
Adding a second field (maybe after a different magic to be backwards-compatible with the current spec) to include the version and other parameters would allow differentiating between binaries built for one version and for another.

Having this information inside a section would work too, but would probably require that section to be the first to interpret the following sections correctly.

How about a magic sequence of 8 bytes, starting with "soil", followed by an 8-bit flags field to encode required features (e.g. HW-multiply, 32-bit support, atomics) and finally three bytes for versioning in major.minor.patch format?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions