rust-lang / rust-lang/rustc_codegen_cranelift

Make the jit work with a cg_llvm libstd

Open
#1,134 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-jit C-bug
Dominant language
Rust
Stars
2.1k
Forks
157
Avg merge
1d 19h
Merged PRs (30d)
3

Description

  • Don't try to load the rust_metadata_* symbol, which is part of a section without the LOAD flag. (25f7eeec4638694bfeb5dc7569701ee802e2bf45)
  • Avoid attempted re-initialization of the current thread's ThreadInfo when the same libstd is used by rustc and the jitted program. (e86b95480fac70673bd837e7fcfa45458bd52eb7)
  • compiler_builtins intrinsics not exported from libstd.so. (94b51d14e6770f6e8cfec4bf4c0d5805caa58143)
  • cg_llvm's libstd.so is compiled with -Cpanic=unwind, while cg_clif always uses -Cpanic=abort.
  • Ensure that is_x86_feature_detected returns false for features unsupported by cg_clif. (optional. only necessary for crates using SIMD) is_x86_feature_detected is not longer being patched.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

No file or test is named. Start by tracing how cg_llvm's libstd panic strategy differs from cg_clif's -Cpanic=abort, then identify the relevant compiler configuration or compatibility path. Done means cg_llvm's libstd works with the JIT without the panic-strategy mismatch.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.