rust-lang / rust-lang/rust

Tracking Issue for RFC 3543 patchable-function-entry

Open
#123,115 2 comments 0 reactions 1 assignee View on GitHub

@nebulark is already working on this.

Since May 5, 2024.

A-rust-for-linux B-RFC-approved C-tracking-issue F-patchable_function_entry T-compiler T-lang
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

This is a tracking issue for the RFC 3543 patchable-function-entry (rust-lang/rfcs#3543).

The feature gate for the issue is #![feature(patchable_function_entry)].

This is support for patchable-function-entry as present in clang and gcc. This feature is generally used to allow hotpatching and instrumentation of code.

About tracking issues

Tracking issues are used to record the overall progress of implementation. They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions. A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature. Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

Steps
Unresolved Questions
  • Should we use LLVM or gcc/clang style for a per-function attribute? Should we support both styles?
  • Should we support a more explicit command line argument style?
  • Should we reject linking crates with different default padding configurations?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.