Tracking Issue for rustc-codegen-gcc-preview

This is a tracking issue for the rustc-codegen-gcc-preview dist/rustup component, and also its associated gcc-<target>-preview component.

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.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

Details

• rustc-codegen-gcc-preview contains the GCC codegen backend for a given host target.
• gcc-<target>-preview contains the GCC (libgccjit) library, which is needed as a dependency of the GCC codegen backend. A separate component is needed for each (host, target) compilation pair, so the gcc component currently embeds the compilation target in its name directly.

Steps

• Write some documentation

Unresolved Questions

• What will it take to transition out of -preview?
• Can we figure out a better mechanism for shipping the libgccjit compilation pairs, rather than embedding the target in the component name?

Implementation history

• https://github.com/rust-lang/rust/pull/150538
• https://github.com/rust-lang/rust/pull/150541
• https://github.com/rust-lang/rust/pull/151156

No target file or test is named. Start by reading the implementation history in PRs #150538, #150541, and #151156, then review the rustc-codegen-gcc repository and the component details in this issue. Done means producing the missing documentation while accounting for the preview components and the unresolved shipping questions.