rust-lang / rust-lang/rustc_codegen_gcc
Backport patches to libgccjit 12
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 105
- Avg merge
- 8h 20m
- Merged PRs (30d)
- 14
Description
To make the code of this codegen simpler, I could backport the patches to libgccjit 12.
GCC policy: https://gcc.gnu.org/develop.html
@joshtriplett: I remember we talked about supporting libgccjit 12 at run-time instead of compile-time, but I'm now wondering if it would be just simpler to backport the GCC patches.
That would allow me to remove a lot of code in the codegen.
Do you see any drawbacks? Do you know if some Linux distros don't do minor version updates of GCC?
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 reading the linked GCC policy and inspecting the codegen paths that handle libgccjit 12. Determine whether backporting the GCC patches is feasible across Linux distributions and whether it would remove the existing runtime or compile-time compatibility code; the issue is done when that approach is resolved and its scope is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100