summaryrefslogtreecommitdiff
path: root/benchmark/vm_lvar_set.yml
diff options
context:
space:
mode:
authorTakashi Kokubun <takashikkbn@gmail.com>2020-04-13 21:37:42 -0700
committerGitHub <noreply@github.com>2020-04-13 21:37:42 -0700
commitf883d6219e107554ebde5dff6d2f8383857f7518 (patch)
tree295da84ed01841281ca7ed0510effa074def19b8 /benchmark/vm_lvar_set.yml
parent9fa24018b761d8902ad430ce604b174cf55062ab (diff)
Unify vm benchmark prefixes to vm_ (#3028)
The vm1_ prefix and vm2_ had had special meaning until 820ad9cb1d72d0897b73dae282df3793814b27e8 and 12068aa4e980ab32a0438408a519030e65dabf5e. AFAIK there's no special meaning in vm3_ prefix. As they have confused people (like "In `benchmark` what is difference between `vm1_`, `vm2_` and `vm3_`"), I'd like to remove the obsoleted prefix as we obviated that two years ago.
Notes
Notes: Merged-By: k0kubun <takashikkbn@gmail.com>
Diffstat (limited to 'benchmark/vm_lvar_set.yml')
-rw-r--r--benchmark/vm_lvar_set.yml4
1 files changed, 4 insertions, 0 deletions
diff --git a/benchmark/vm_lvar_set.yml b/benchmark/vm_lvar_set.yml
new file mode 100644
index 0000000000..f29f763d81
--- /dev/null
+++ b/benchmark/vm_lvar_set.yml
@@ -0,0 +1,4 @@
+benchmark:
+ vm_lvar_set: |
+ a = b = c = d = e = f = g = h = j = k = l = m = n = o = p = q = r = 1
+loop_count: 30000000