Add initial benchmark setup

[lockshaw]

Description of changes:

• Add benchmark suites for entries under lib (specifically compiler and utils as a starting point)
• Add support to proj for running benchmarks (run proj benchmark) and profiling (see proj profile -h)
• Add nix dependencies for eventually setting up CI support for tracking performance regressions in benchmarks (will be done in a future PR: see Add CI support for benchmarks #1596)
• Add libassert as a dependency (not really related to benchmarking, but just bundled in with this PR)

Related Issues:

Linked Issues:

• Issue Add CI support for benchmarks #1596

Issues closed by this PR:

• Closes #

---

This change is 

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 0.00%. Comparing base (10ef31b) to head (0caa4ae).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #1591       +/-   ##
==========================================
- Coverage   62.90%       0   -62.91%     
==========================================
  Files         635       0      -635     
  Lines       15201       0    -15201     
==========================================
- Hits         9562       0     -9562     
+ Misses       5639       0     -5639     

Flag	Coverage Δ
unittests	?

Flags with carried forward coverage won't be shown. Click here to find out more.

see 635 files with indirect coverage changes

[Marsella8]

Reviewed 3 of 23 files at r1, 17 of 20 files at r2, all commit messages.
Reviewable status: 20 of 23 files reviewed, 3 unresolved discussions (waiting on @chenzhuofu)

---

lib/compiler/benchmark/src/compiler/series_parallel/computation_graph/get_computation_graph_series_parallel_decomposition.cc line 13 at r2 (raw file):

static void benchmark_get_computation_graph_series_parallel_decomposition(
    benchmark::State &state, ComputationGraph const &cg) {
  // ComputationGraph cg = state.range(0);

remove

---

lib/compiler/benchmark/src/compiler/series_parallel/computation_graph/get_computation_graph_series_parallel_decomposition.cc line 30 at r2 (raw file):

    get_transformer_computation_graph(get_default_transformer_config()));

BENCHMARK_CAPTURE(benchmark_get_computation_graph_series_parallel_decomposition,

is there a slightly better syntax for benchmarking across a set of different values? This isn't bad obviously.

---

lib/utils/include/utils/archetypes/ordered_value_type.h line 14 at r2 (raw file):

  ordered_value_type(ordered_value_type const &) {
    PANIC();

the libassert asserts seem to be a lot nicer trace-wise compared to the cassert ones, maybe worth it to move all assert logic to libassert? We could also use -DLIBASSERT_LOWERCASE to alias assert to libasserts assert. (Obviously for a future PR).

[lockshaw]

Reviewable status: 20 of 23 files reviewed, 3 unresolved discussions (waiting on @chenzhuofu and @Marsella8)

---

lib/compiler/benchmark/src/compiler/series_parallel/computation_graph/get_computation_graph_series_parallel_decomposition.cc line 13 at r2 (raw file):

Previously, Marsella8 wrote…

remove

Done.

---

lib/compiler/benchmark/src/compiler/series_parallel/computation_graph/get_computation_graph_series_parallel_decomposition.cc line 30 at r2 (raw file):

Previously, Marsella8 wrote…

is there a slightly better syntax for benchmarking across a set of different values? This isn't bad obviously.

You can do numerical ranges (e.g., see transitive_closure.cc), but for arbitrary sets of values, no. I also wish there was a better method for this, but for now gtest seemed to have the best compromise in terms of features--I'm not against moving to something different later once we have a better idea of how we use the benchmarks

---

lib/utils/include/utils/archetypes/ordered_value_type.h line 14 at r2 (raw file):

Previously, Marsella8 wrote…

the libassert asserts seem to be a lot nicer trace-wise compared to the cassert ones, maybe worth it to move all assert logic to libassert? We could also use -DLIBASSERT_LOWERCASE to alias assert to libasserts assert. (Obviously for a future PR).

Yup, that's the plan! We may even replace mk_runtime_error with libassert, as libassert allows us to override the error handling behavior so we could still do exception throwing but more easily and better error messages