chore: remove op_baseline and flamebench (#21120)

ops are better tested in deno_core, and flamebench has rotted quite a
bit.

1 files changed, 0 insertions, 29 deletions

diff --git a/tools/README.md b/tools/README.md
index 0c9607380..f30e16b8f 100644
--- a/tools/README.md
+++ b/tools/README.md
@@ -31,35 +31,6 @@ executable
 cargo run -- run --allow-read --allow-write --allow-run --unstable ./tools/<script>
 ```
 
-## flamebench.js
-
-`flamebench.js` facilitates profiling and generating flamegraphs from
-benchmarks.
-
-General usage:
-
-```
-❯ ./tools/flamebench.js
-flamebench <bench_name> [bench_filter]
-
-Available benches:
-op_baseline
-ser
-de
-```
-
-To profile the `op_baseline` bench, run `./tools/flamebench.js op_baseline`,
-this will run all 3 benches in `op_baseline.
-
-Often when profiling/optimizing, you'll want to focus on a specific sub-bench,
-`flamebench` supports a bench/test filter arg like the regular cargo commands.
-So you can simply run `./tools/flamebench.js op_baseline bench_op_async` or
-`./tools/flamebench.js op_baseline bench_op_nop` to profile specific benches.
-
-Tip: the `[bench_filter]` argument doesn't have to be an exact bench name, you
-can use a shorthand or a partial match to profile a group of benches, e.g:
-`./tools/flamebench.js de v8`
-
 ## copyright_checker.js
 
 `copyright_checker.js` is used to check copyright headers in the codebase.