Add support to caller location #62
Assignees
Comments
celinval
added a commit
to celinval/kani-dev
that referenced
this issue
Feb 6, 2024
Use FnAbi instead of function signature when generating code for function types. Properly check the `PassMode::Ignore`. For foreign functions, instead of ignoring the declaration type, cast the arguments and return value. For now, we also ignore the caller location, since we don't currently support tracking caller location. This change makes it easier for us to do so. We might want to wait for this issue to get fixed so we can easily add support using stable APIs: rust-lang/project-stable-mir#62
celinval
added a commit
to model-checking/kani
that referenced
this issue
Feb 6, 2024
Use FnAbi instead of function signature when generating code for function types. Properly check the `PassMode::Ignore`. For foreign functions, instead of ignoring the declaration type, cast the arguments and return value. For now, we also ignore the caller location, since we don't currently support tracking caller location. This change makes it easier for us to do so. We might want to wait for this issue to get fixed so we can easily add support using stable APIs: rust-lang/project-stable-mir#62 Resolves #2260 Resolves #2312 Resolves #1365 Resolves #1350
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The ABI of functions with
#[track_caller]include the caller location as an argument, however, we don't have any mechanism to generate the expected Location. We should add support for it.For more details, see https://rustc-dev-guide.rust-lang.org/backend/implicit-caller-location.html.
The text was updated successfully, but these errors were encountered: