When running code with ctrack on Compiler Explorer, the output does show results, but many strings in the table are damaged:
+-------------+--------------------------------+------+----------+----------+----------+-------+---------+
|Unknown codeUnknown code filename |Unknown codeUnknown code function |Unknown codeUnknown code line |Unknown codeUnknown code time acc |Unknown codeUnknown code sd |Unknown codeUnknown code cv |Unknown codeUnknown code calls |Unknown codeUnknown code threads |Unknown codeUnknown code
+-------------+--------------------------------+------+----------+----------+----------+-------+---------+
| example.cpp | getSizeAfterFilter12345Classic | 1026 | 27.42 ms | 5.79 mcs | 0.211212 | 1000 | 1 |
+-------------+--------------------------------+------+----------+----------+----------+-------+---------+
See https://godbolt.org/z/5oa5ffsMx for a full example.
I am aware the running benchmarks in the cloud does not yield very useful results, but tools such as compiler explorer are valuable to share, discuss and improve the benchmarked code.
When running code with ctrack on Compiler Explorer, the output does show results, but many strings in the table are damaged:
See https://godbolt.org/z/5oa5ffsMx for a full example.
I am aware the running benchmarks in the cloud does not yield very useful results, but tools such as compiler explorer are valuable to share, discuss and improve the benchmarked code.