New upstream version 1.44.1+dfsg1

[rustc.git] / src / doc / rustc-dev-guide / src / profiling.md

diff --git a/src/doc/rustc-dev-guide/src/profiling.md b/src/doc/rustc-dev-guide/src/profiling.md
index b7cc72258c1e006b577b9bc2f9e4a76e8506ec5e..8eaa8e94f1e6f28a214fa7a517c8617a813c9a9f 100644 (file)
--- a/src/doc/rustc-dev-guide/src/profiling.md
+++ b/src/doc/rustc-dev-guide/src/profiling.md
@@ -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.