See if -fno-semantic-interposition should be the default
Open
Nobody has claimed this yet.
GCC
Rust Integrations
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 231
- Avg merge
- 19h 55m
- Merged PRs (30d)
- 67
Description
Could not find a quick answer as to what is rustc doing.
GCC defaults to having semantic interposition, but at least clang does not (see https://maskray.me/blog/2021-05-09-fno-semantic-interposition for example).
As rustc/gccrs are producing PI[E/C], this option will have an impact on generated code.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing how rustc, GCC and clang handle semantic interposition and the effects of -fno-semantic-interposition on generated PIE/PIC code. Determine whether gccrs should change its default and define the expected generated-code or performance behavior before locating the relevant compiler option handling and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100