Difference between revisions of "DRuntime development"
(Init) |
(phobos -> druntime) |
||
| Line 2: | Line 2: | ||
If you need help you can ask questions on <code>#d</code> IRC channel on freenode.org ([https://kiwiirc.com/client/irc.freenode.net/d web interface]) or on [http://forum.dlang.org/ our forum]. | If you need help you can ask questions on <code>#d</code> IRC channel on freenode.org ([https://kiwiirc.com/client/irc.freenode.net/d web interface]) or on [http://forum.dlang.org/ our forum]. | ||
| − | This section explains commonly commands which are commonly used to test the D | + | This section explains commonly commands which are commonly used to test the low level runtime library for the D programming language. |
Revision as of 23:18, 11 December 2017
Welcome to the D community and thanks for your interest in contributing!
If you need help you can ask questions on #d IRC channel on freenode.org (web interface) or on our forum.
This section explains commonly commands which are commonly used to test the low level runtime library for the D programming language.
Run all tests
make -f posix.mak unittest -j4
Run an individual test
Sometimes it can be helpful to rerun only a single test which tests the module or feature one is working on:
make -f posix.mak test/coverage/.run
Run benchmark
If you are making a bigger change or want to improve the performance of a specific function in druntime, you should run the included benchmark script:
rdmd benchmark/runbench.d
