[Issue 14502] dmd -O optimization breaks app

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=14502

--- Comment #7 from Vladimir Panteleev <thecybershadow at gmail.com> ---
(In reply to Tomáš Chaloupka from comment #6)
> dustmite is problematic because it can lead to versions which segfaults too,
> but with other reason or which eats all mem, etc. And is slow as hell to
> test outputs from all variants (-O -release, -release, -debug) - I let it
> run for more than 24hours actually with just slightly shorter version..

Um, did you read the linked page?

Your test script should do the following:

1. Compile the program without -O
2. Run the program and check that it exits successfully. You can use "timeout"
and "ulimit" to limit how much time and memory the program can consume.
3. If the above program works fine, compile it again with -O
4. Run the program and checks that it crashes (or produces output different
from the first run)
5. If the first run was OK and the second run crashed, return 0 (you have
reproduced the bug). Otherwise, return 1

--