delta/ruby.git/ext/coverage/coverage.c, branch ruby_3_2 github.com: ruby/ruby.git Fix typos (#6775) 2022-11-21T05:07:18+00:00 Yudai Takada 13041216+ydah@users.noreply.github.com 2022-11-21T05:07:18+00:00 29e6d97517bbd4dcc540464c8473172232f3e228 * s/Innteger/Integer/ * s/diretory/directory/ * s/Bufer/Buffer/ * s/defalt/default/ * s/covearge/coverage/ 
* s/Innteger/Integer/

* s/diretory/directory/

* s/Bufer/Buffer/

* s/defalt/default/

* s/covearge/coverage/
 Add `Coverage.supported?` to detect what modes are supported. 2022-09-28T20:44:14+00:00 Samuel Williams samuel.williams@oriontransfer.co.nz 2022-09-28T11:08:03+00:00 bd2fbd35888413217337dd327ad90015c0322d12 






Add `eval: true/false` flag to `Coverage.setup`.
2022-09-28T20:44:14+00:00

Samuel Williams
samuel.williams@oriontransfer.co.nz

2022-09-28T10:35:42+00:00

9dd902b83186ad6f9d0a553da2ca114bac6ab7b5












Expand tabs [ci skip]
2022-07-21T16:42:04+00:00

Takashi Kokubun
takashikkbn@gmail.com

2022-07-21T16:23:58+00:00

5b21e94bebed90180d8ff63dad03b8b948361089

[Misc #18891]





[Misc #18891]







Fix typos
2021-11-02T10:17:37+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2021-11-02T09:29:53+00:00

a2024081805af4e729bea029abb7bbe7c383dce2












Make Coverage suspendable (#4856)
2021-10-25T11:00:51+00:00

Yusuke Endoh
mame@ruby-lang.org

2021-10-25T11:00:51+00:00

86e3d77abb8a033650937710d1ab009e98647494

* Make Coverage suspendable

Add `Coverage.suspend`, `Coverage.resume` and some methods.

[Feature #18176] [ruby-core:105321]




* Make Coverage suspendable

Add `Coverage.suspend`, `Coverage.resume` and some methods.

[Feature #18176] [ruby-core:105321]






Document Different Coverage Modes
2020-11-20T00:24:46+00:00

Kevin Murphy
murphy.kevin.mail@gmail.com

2020-11-19T21:38:43+00:00

0026f644d739efed0d69911b434a1012ad55c393

This commits adds in documentation to illustrate the different modes you
can start coverage with. Examples are provided to show how to start each
of these modes, along with an explanation of the mode and a description
of the output.





This commits adds in documentation to illustrate the different modes you
can start coverage with. Examples are provided to show how to start each
of these modes, along with an explanation of the mode and a description
of the output.







make ext/coverage ASAN friendly
2020-09-28T15:20:23+00:00

Aaron Patterson
tenderlove@ruby-lang.org

2020-09-25T21:55:12+00:00

b328b830264408b467a5c904a474e7112c5d678c












RHASH_TBL: is now ext-only
2020-08-19T06:10:53+00:00

卜部昌平
shyouhei@ruby-lang.org

2020-08-17T02:12:23+00:00

99093e1600ccef17ab99356b689573fcfd336ecc

It seems almost no internal codes use RHASH_TBL any longer.  Why not
just eliminate it entirely, so that the macro can be purely ext-only.





It seems almost no internal codes use RHASH_TBL any longer.  Why not
just eliminate it entirely, so that the macro can be purely ext-only.







compile.c: Improve branch coverage instrumentation [Bug #16967]
2020-06-20T00:28:03+00:00

Yusuke Endoh
mame@ruby-lang.org

2020-06-19T05:52:35+00:00

50efa18c6cf102e070ba0f95edc01c72516495a3

Formerly, branch coverage measurement counters are generated for each
compilation traverse of the AST.  However, ensure clause node is
traversed twice; one is for normal-exit case (the resulted bytecode is
embedded in its outer scope), and the other is for exceptional case (the
resulted bytecode is used in catch table).  Two branch coverage counters
are generated for the two cases, but it is not desired.

This changeset revamps the internal representation of branch coverage
measurement.  Branch coverage counters are generated only at the first
visit of a branch node.  Visiting the same node reuses the
already-generated counter, so double counting is avoided.





Formerly, branch coverage measurement counters are generated for each
compilation traverse of the AST.  However, ensure clause node is
traversed twice; one is for normal-exit case (the resulted bytecode is
embedded in its outer scope), and the other is for exceptional case (the
resulted bytecode is used in catch table).  Two branch coverage counters
are generated for the two cases, but it is not desired.

This changeset revamps the internal representation of branch coverage
measurement.  Branch coverage counters are generated only at the first
visit of a branch node.  Visiting the same node reuses the
already-generated counter, so double counting is avoided.