mirror of
https://github.com/carbon-language/carbon-lang.git
synced 2026-10-01 07:35:02 +01:00
This PR adds a `--dump-timings` flag to the `compile` subcommand (similar to the existing `--dump-mem-usage` flag), which collects timing data per compilation unit for each compilation phase. For example, on my 2020 M1 MacBook: ``` $ bazel build -c opt //toolchain $ bazel-bin/toolchain/install/run_carbon compile --phase=lower --dump-timings examples/sieve.carbon | tail ... --- filename: 'examples/sieve.carbon' nanoseconds: lex: 30792 parse: 25458 check: 226625 lower: 1136958 Total: 1419833 ... ``` Most of the changes are pretty straightforward. There were a couple I wasn't sure about though; let me know if I should change: - new `Timings` class in its own file, pretty similar to the existing `MemUsage` class - added a `timings_` field to the `CompilationUnit` class - added a `timings` field to the `Check::Unit` struct - renamed `CheckParseTree` function to `CheckParseTreeInner` for ease of timing with early `return` --------- Co-authored-by: Jon Ross-Perkins <jperkins@google.com>
22 lines
882 B
Plaintext
22 lines
882 B
Plaintext
// Part of the Carbon Language project, under the Apache License v2.0 with LLVM
|
|
// Exceptions. See /LICENSE for license information.
|
|
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
|
|
//
|
|
// ARGS: compile --dump-timings --phase=check %s
|
|
//
|
|
// SET-CHECK-SUBSET
|
|
//
|
|
// NOAUTOUPDATE
|
|
// TIP: To test this file alone, run:
|
|
// TIP: bazel test //toolchain/testing:file_test --test_arg=--file_tests=toolchain/driver/testdata/dump_timings.carbon
|
|
// TIP: To dump output, run:
|
|
// TIP: bazel run //toolchain/testing:file_test -- --dump_output --file_tests=toolchain/driver/testdata/dump_timings.carbon
|
|
|
|
// CHECK:STDOUT: filename: dump_timings.carbon
|
|
// CHECK:STDOUT: nanoseconds:
|
|
// CHECK:STDOUT: lex: {{\d+}}
|
|
// CHECK:STDOUT: parse: {{\d+}}
|
|
// CHECK:STDOUT: check: {{\d+}}
|
|
// CHECK:STDOUT: Total: {{\d+}}
|
|
// CHECK:STDOUT: ...
|