Add SPEC launcher

JOURNAL.md

@@ -5149,3 +5149,27 @@ and "integer" variants and removing a couple of large benchmarks.
 
 Still, the closure is gigantic, as they are collecting the environment during
 the build phase and that makes the result depend on the build packages.
+
+## 2024-10-09
+
+One of the problems with the `speccmds.cmd` file is that is assumes that it can
+write the output of the benchmarks in the same place that the binaries are
+located.
+
+    hut% cat benchspec/CPU/602.gcc_s/run/run_base_test_nix-m64.0000/speccmds.cmd
+    -r
+    -N C
+    -C /build/out/benchspec/CPU/602.gcc_s/run/run_base_test_nix-m64.0000
+    -o t1.opts-O3_-finline-limit_50000.out -e t1.opts-O3_-finline-limit_50000.err ../run_base_test_nix-m64.0000/sgcc_base.nix-m64 t1.c -O3 -finline-limit=50000 -o t1.opts-O3_-finline-limit_50000.s > t1.opts-O3_-finline-limit_50000.out 2>> t1.opts-O3_-finline-limit_50000.err
+
+We can address this problem by modifying the `-C ...` command and just use `-C
+602.gcc_s` (not sure if it creates it directly). Then we need to modify the
+../run... part to use the full path of the binary.
+
+    hut% cat speccmds.cmd | sed '/^-C/d'
+    -r
+    -N C
+    -o t1.opts-O3_-finline-limit_50000.out -e t1.opts-O3_-finline-limit_50000.err ../run_base_test_nix-m64.0000/sgcc_base.nix-m64 t1.c -O3 -finline-limit=50000 -o t1.opts-O3_-finline-limit_50000.s > t1.opts-O3_-finline-limit_50000.out 2>> t1.opts-O3_-finline-limit_50000.err
+
+I can create a symlink to the benchmark directory, so it finds it at
+`../run_base_test_nix-m64.0000`.