Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Strict provenance unwind #114534

Merged
merged 2 commits into from
Oct 19, 2023
Merged

Strict provenance unwind #114534

merged 2 commits into from
Oct 19, 2023

Commits on Oct 10, 2023

  1. Use pointers instead of usize addresses for landing pads 

    This bring unwind and personality code more in line with strict-provenance
    @niluxv
    niluxv committed Oct 10, 2023
    Configuration menu
    Copy the full SHA
    e7a3c34 View commit details
    Browse the repository at this point in the history

  2. Rewrite read_encoded_pointer conforming to strict provenance 

    * Entries in the callsite table now use a dedicated function for reading an offset rather than a pointer
* `read_encoded_pointer` uses that new function for reading offsets when the "application" part of the encoding indicates an offset (relative to some pointer)
* It now errors out on nonsensical "application" and "value encoding" combinations

Inspired by @eddyb's comment on zulip about this:
<https://rust-lang.zulipchat.com/#narrow/stream/136281-t-opsem/topic/strict.20provenance.20in.20dwarf.3A.3Aeh/near/276197290>
    @niluxv
    niluxv committed Oct 10, 2023
    Configuration menu
    Copy the full SHA
    b48039f View commit details
    Browse the repository at this point in the history