You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10-1Lines changed: 10 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -169,19 +169,28 @@ The flag effect plot shows the effect of specified configuration flags against a
169
169
In `bench_runner.toml`, the `flag_effect_plot` table has a `subplots` key which is an array of tables with the following keys:
170
170
171
171
-`name`: The description of the flags to use in the title.
172
+
-`version`: The version series to compare. Should be a 2-part version, e.g. "3.14"
172
173
-`head_flags`: A list of flags to use as the head.
173
174
-`base_flags`: (optional) A list of flags to use as the base. By default, this is a default build, i.e. no flags.
174
-
-`runner_map`: (optional) If you need to map a runner to a base in a different runner, you can provide that mapping here. For example, with tail-calling, you may want to compare runners configured to use clang against runners configured with the "default compiler" for a given platform. The mapping is from the "head" runner nickname to the "base" runner nickname.
175
+
-`runner_map`: (optional) If you need to map a runner to a base in a
176
+
different runner, you can provide that mapping here. For example, with
177
+
tail-calling, you may want to compare runners configured to use clang
178
+
against runners configured with the "default compiler" for a given
179
+
platform. The mapping is from the "head" runner nickname to the "base"
180
+
runner nickname. If `runner_map` is not empty, only the "head" runners in
0 commit comments