ruby--ruby/benchmark/vm_module_const_set.yml

prelude: |
  module M
  end
  $VERBOSE = nil
benchmark:
  vm_module_const_set: |
    M.const_set(:X, Module.new)
loop_count: 6000000
benchmark/vm2_*.yml: abstract away the while loop git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@63896 b2dd03c8-39d4-4d8f-98ff-823fe69b080e 2018-07-08 13:03:23 -04:00			`prelude: \|`
			`module M`
			`end`
			`$VERBOSE = nil`
benchmark: convert bm_vm2_.rb to vm2_.yml This YAML transformation is needed to support whileloop2 time substituion by benchmark_driver.gem later. This commmit changes no benchmark behavior. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@63892 b2dd03c8-39d4-4d8f-98ff-823fe69b080e 2018-07-08 11:35:22 -04:00			`benchmark:`
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. 2020-04-14 00:37:42 -04:00			`vm_module_const_set: \|`
benchmark/vm2_*.yml: abstract away the while loop git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@63896 b2dd03c8-39d4-4d8f-98ff-823fe69b080e 2018-07-08 13:03:23 -04:00			`M.const_set(:X, Module.new)`
			`loop_count: 6000000`