Skip to content

Footnotes in the "Single-origin provenance" section are outdated #49

@brooksdavis

Description

@brooksdavis

Footnote 1 says "Historically, the CHERI compiler would select the left-hand-most pointer in the expression as the provenance source.". This is still true, we just warn about it.

Footnote 2 says "We could add a data-flow-sensitive analysis to determine whether values are the result of promotion from a non-provenance-carrying type." We should note that such analysis would almost certainly occur after optimization passes and thus would have optimization dependent results. It would not be dependable either for generating compile time warning or at runtime for program correctness purposes. Such analysis could be used to inform the correct annotations in code.

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