rustc-dev-guide
rustc-dev-guide copied to clipboard
A guide to how rustc works and how to contribute to it.
Due to changes by https://github.com/rust-lang/rust/pull/100377
## Procedure Each of these dates should be checked to see if the docs they annotate are up-to-date. Each date should be updated (in the Markdown file where it appears)...
Dependent on getting https://github.com/rust-lang/rust/pull/83234 merged first. cc @rust-lang/wg-const-eval
_Originally posted by @rylev in https://github.com/rust-lang/rustc-dev-guide/pull/1406#pullrequestreview-1049224734_: > This also seems correct though some of the information provided seems more relevant for *users* of Rust rather than those working on the...
It looks like this is out-of-date, since [`Place`](https://doc.rust-lang.org/nightly/nightly-rustc/rustc_middle/mir/struct.Place.html) is a struct, not an enum. https://github.com/rust-lang/rustc-dev-guide/blob/9d2081110a3e2bc5f1c95ebd830f92d6fe1c2942/src/mir/index.md#L238-L247
The location of the demangler was never linked to in the guide on using a debugger in the compiler. Originally noted [here](https://github.com/rust-lang/rustc-dev-guide/pull/316#discussion_r283062536).
This provides more in-depth descriptions of the parallelism occurring during codegen. There are probably a few things I got wrong conceptually, so don't hesitate to point them out :)
(compare https://highlightjs.readthedocs.io/en/latest/supported-languages.html for a list of languages and their identifiers/aliases) Motivation: This code block was mishighlighted: https://rustc-dev-guide.rust-lang.org/git.html#i-see--head
https://rustc-dev-guide.rust-lang.org/tests/running.html#running-tests-manually explains how to run the tests manually. However, it does not explain how to do this for check-pass and build-pass tests. I assume for build-pass it might just be...