DMD development

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 dmd D Programming Language compiler.

Tests

The testsuite is in ~/dlang/dmd/test. Please go to this directory.

cd ~/dlang/dmd/test

The testsuite will always print the exact command used to run a test, s.t. it's easy to single out and reproduce a failure.

Running all tests

./run.d

The testsuite runner will automatically use all available threads. You can use e.g. -j1 to e.g. use one thread.

Run a specific test category

./run.d fail_compilation

Run a specific test

./run.d fail_compilation/ice12673.d

Run a set of specific tests

./run.d fail_compilation/ice*

Automatically update the OUTPUT text

./run.d fail_compilation AUTO_UPDATE=1

A second run might be required.

Remove test states

./run.d clean

Run unittests within the compiler

There are a few unittest blocks within the compiler and there usage is increasing. They can be tested with:

cd ~/dlang/dmd/src
make -f posix.mak unittest

Old Makefile targets

The following section explains the Makefile rules of the test/Makefile. It has been replaced by test/run.d and is only listed here for users who experience problems during the transition to

run.d

Running the testsuite on Windows

If you run the testsuite on Windows, make sure you install have the following installed:

• Bash environment (e.g. Git for Windows or MYS)
• GNUMake (a bit harder to find, see the built binaries of this PR or use mingw32-make.exe from a MinGW binary)

Digger can install this automatically for you.

If you are looking for an automated way to turn a VirtualBox in a Development Machine, follow these instructions to create a ssh-accessible Windows box.

Important: you need to use GNU make to run the Makefile in test - not the DigitalMars make that is bundled with D's Windows binaries. DigitalMars make is only required for win32.mak and win64.mak.

Run all tests which haven't been run before

make all -j8

If you you now rerun this command, the testsuite won't execute anything:

make all -j8

However, if you modified the compiler, it will only rerun the failing tests as these don't have an output stored.

Remove test states

The test suite stores the results of run tests to allow re-running only the failed tests. This state is stored in `~/dlang/dmd/test/test_results` and can be removed with:

make clean

Always run all tests

make run_tests -j8

Run an individual test

Sometimes it can be helpful to rerun only a single test which tests the fix or feature one is working on:

make test_results/compilable/test10066.d.out

If you want to force re-evaluation of a single test, simply remove the respective file:

rm test_results/compilable/test10066.d.out
make test_results/compilable/test10066.d.out

Run quick test

Often one makes a small change and wants to quickly know whether this change completely broke the compiler. For this, the target make quick exists:

make quick

Run group of tests

Sometimes it can be useful to run only a subset of tests. The testsuite groups the test in three groups: runnable, compilable and failed_compilation. They can be run individually:

make run_runnable_tests:         # run just the runnable tests
make run_compilable_tests:       # run just the compilable tests
make run_fail_compilation_tests  # run just the fail compilation tests