Update some projects locations (#658)
This commit is contained in:
parent
8a1879a279
commit
27269235d3
|
|
@ -261,8 +261,8 @@ until it finds the regression. You can then look at the PR to get more context
|
|||
on *why* it was changed. See [this tutorial][bisect-tutorial] on how to use
|
||||
it.
|
||||
|
||||
[bisect]: https://github.com/rust-lang-nursery/cargo-bisect-rustc
|
||||
[bisect-tutorial]: https://github.com/rust-lang-nursery/cargo-bisect-rustc/blob/master/TUTORIAL.md
|
||||
[bisect]: https://github.com/rust-lang/cargo-bisect-rustc
|
||||
[bisect-tutorial]: https://github.com/rust-lang/cargo-bisect-rustc/blob/master/TUTORIAL.md
|
||||
|
||||
## Downloading Artifacts from Rust's CI
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ enforced by a script we affectionately call the "tidy" script. The
|
|||
tidy script runs automatically when you do `./x.py test` and can be run
|
||||
in isolation with `./x.py test tidy`.
|
||||
|
||||
[fmt]: https://github.com/rust-lang-nursery/fmt-rfcs
|
||||
[fmt]: https://github.com/rust-dev-tools/fmt-rfcs
|
||||
|
||||
<a name="copyright"></a>
|
||||
|
||||
|
|
|
|||
|
|
@ -82,7 +82,7 @@ is passed) as JSON for consumption by tools, most notably the [Rust Language
|
|||
Server][rls] and [`rustfix`][rustfix].
|
||||
|
||||
[rls]: https://github.com/rust-lang/rls
|
||||
[rustfix]: https://github.com/rust-lang-nursery/rustfix
|
||||
[rustfix]: https://github.com/rust-lang/rustfix
|
||||
|
||||
Not all suggestions should be applied mechanically. Use the
|
||||
[`span_suggestion`][span_suggestion] method of `DiagnosticBuilder` to
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ This section talks about how to profile the compiler and find out where it spend
|
|||
Depending on what you're trying to measure, there are several different approaches:
|
||||
|
||||
- If you want to see if a PR improves or regresses compiler performance:
|
||||
- The [rustc-perf](https://github.com/rust-lang-nursery/rustc-perf) project makes this easy and can be triggered to run on a PR via the `@rustc-perf` bot.
|
||||
- The [rustc-perf](https://github.com/rust-lang/rustc-perf) project makes this easy and can be triggered to run on a PR via the `@rustc-perf` bot.
|
||||
|
||||
- If you want a medium-to-high level overview of where `rustc` is spending its time:
|
||||
- The `-Zself-profile` flag and [measureme](https://github.com/rust-lang/measureme) tools offer a query-based approach to profiling.
|
||||
|
|
|
|||
|
|
@ -59,10 +59,10 @@ do that, the first step is to clone
|
|||
[the rustc-perf repository][rustc-perf-gh]:
|
||||
|
||||
```bash
|
||||
git clone https://github.com/rust-lang-nursery/rustc-perf
|
||||
git clone https://github.com/rust-lang/rustc-perf
|
||||
```
|
||||
|
||||
[rustc-perf-gh]: https://github.com/rust-lang-nursery/rustc-perf
|
||||
[rustc-perf-gh]: https://github.com/rust-lang/rustc-perf
|
||||
|
||||
#### Doing it the easy way
|
||||
|
||||
|
|
@ -70,7 +70,7 @@ Once you've cloned the repo, you can use the `collector` executable to
|
|||
do profiling for you! You can find
|
||||
[instructions in the rustc-perf readme][rustc-perf-readme].
|
||||
|
||||
[rustc-perf-readme]: https://github.com/rust-lang-nursery/rustc-perf/blob/master/collector/README.md#profiling
|
||||
[rustc-perf-readme]: https://github.com/rust-lang/rustc-perf/blob/master/collector/README.md#profiling
|
||||
|
||||
For example, to measure the clap-rs test, you might do:
|
||||
|
||||
|
|
@ -94,7 +94,7 @@ are found in [the `collector/benchmarks` directory][dir]. So let's go
|
|||
into the directory of a specific test; we'll use `clap-rs` as an
|
||||
example:
|
||||
|
||||
[dir]: https://github.com/rust-lang-nursery/rustc-perf/tree/master/collector/benchmarks
|
||||
[dir]: https://github.com/rust-lang/rustc-perf/tree/master/collector/benchmarks
|
||||
|
||||
```bash
|
||||
cd collector/benchmarks/clap-rs
|
||||
|
|
|
|||
|
|
@ -183,7 +183,7 @@ communicate with the server to coordinate running tests (see
|
|||
|
||||
## Crater
|
||||
|
||||
[Crater](https://github.com/rust-lang-nursery/crater) is a tool for compiling
|
||||
[Crater](https://github.com/rust-lang/crater) is a tool for compiling
|
||||
and running tests for _every_ crate on [crates.io](https://crates.io) (and a
|
||||
few on GitHub). It is mainly used for checking for extent of breakage when
|
||||
implementing potentially breaking changes and ensuring lack of breakage by
|
||||
|
|
|
|||
|
|
@ -43,7 +43,7 @@ In terms of code, these types are defined in
|
|||
|
||||
[pphhf]: ./bibliography.html#pphhf
|
||||
[traits_mod]: https://github.com/rust-lang/rust/blob/master/src/librustc_middle/traits/mod.rs
|
||||
[chalk_ir]: https://github.com/rust-lang-nursery/chalk/blob/master/chalk-ir/src/lib.rs
|
||||
[chalk_ir]: https://github.com/rust-lang/chalk/blob/master/chalk-ir/src/lib.rs
|
||||
|
||||
<a name="domain-goals"></a>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue