Profile incremental compilation hashing fingerprints

[rylev]

Adds profiling instrumentation for the hashing of incremental compilation fingerprints per query.

This will eventually feed into the measureme and rustc-perf infrastructure for tracking if computing hashes changes over time.

TODOs:

• Address the FIXME where we are including node interning in the hash timing.
• Update measureme/summarize to handle this new data: Handle new self-profiling information for incr-comp hash fingerprints measureme#166
• Update rustc-perf to handle the new data from measureme (will be done at a later time)

r? @ghost

cc @michaelwoerister

[michaelwoerister]

I left a few comments below.

[rylev]

r? @wesleywiser

[wesleywiser]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[bors]

⌛ Trying commit b5bec17 with merge c9fc2e1e84356aa00676a311f656a51d6f8abdc0...

[bors]

☀️ Try build successful - checks-actions
Build commit: c9fc2e1e84356aa00676a311f656a51d6f8abdc0 (c9fc2e1e84356aa00676a311f656a51d6f8abdc0)

[rust-timer]

Queued c9fc2e1e84356aa00676a311f656a51d6f8abdc0 with parent 5c0ca08, future comparison URL.

[rust-timer]

Finished benchmarking try commit (c9fc2e1e84356aa00676a311f656a51d6f8abdc0): comparison url.

Summary: This benchmark run did not return any significant changes.

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up.

@bors rollup=never
@rustbot label: +S-waiting-on-review -S-waiting-on-perf -perf-regression

[wesleywiser]

This looks good to me and will be quite useful as well! Thanks 🙂

[wesleywiser]

@bors r+

[bors]

📌 Commit b5bec17 has been approved by wesleywiser

[bors]

⌛ Testing commit b5bec17 with merge e41ba3635dd798f0aeccae91b2d19f372e0f85ec...

[rust-log-analyzer]

The job x86_64-apple failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)

      Memory: 14 GB
      Boot ROM Version: VMW71.00V.13989454.B64.1906190538
      Apple ROM Info: [MS_VM_CERT/SHA1/27d66596a61c48dd3dc7216fd715126e33f59ae7]Welcome to the Virtual Machine
      SMC Version (system): 2.8f0
      Serial Number (system): VMqUj3dBSPC6

hw.ncpu: 3
hw.byteorder: 1234
+ ./x.py --stage 2 test
---
[ 26%] Building X86GenCallingConv.inc...
[ 26%] Building X86GenDAGISel.inc...
[ 26%] Building CXX object tools/llvm-cxxmap/CMakeFiles/llvm-cxxmap.dir/llvm-cxxmap.cpp.o
error: Connection to server timed out
make[2]: *** [tools/llvm-cxxmap/CMakeFiles/llvm-cxxmap.dir/llvm-cxxmap.cpp.o] Error 2
make[1]: *** [tools/llvm-cxxmap/CMakeFiles/llvm-cxxmap.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 26%] Building X86GenDisassemblerTables.inc...
[ 26%] Building RISCVGenSearchableTables.inc...
[ 26%] Building X86GenEVEX2VEXTables.inc...
[ 26%] Building RISCVGenSubtargetInfo.inc...
---
[ 27%] Building X86GenRegisterBank.inc...
[ 27%] Building X86GenRegisterInfo.inc...
[ 27%] Building X86GenSubtargetInfo.inc...
[ 27%] Built target X86CommonTableGen
make: *** [all] Error 2
command did not execute successfully, got: exit status: 2
 finished in 2929.849 seconds

Build completed unsuccessfully in 1:48:21
Build completed unsuccessfully in 1:48:21
build script failed, must exit now', /Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/cmake-0.1.44/src/lib.rs:885:5

[bors]

💔 Test failed - checks-actions

[michaelwoerister]

error: Connection to server timed out

Looks like a spurious error during LLVM build. Let's give it another try.

@bors retry

[bors]

⌛ Testing commit b5bec17 with merge f913a4f...

[bors]

☀️ Test successful - checks-actions
Approved by: wesleywiser
Pushing f913a4f to master...