On Sunday, 28 July 2019 at 21:32:38 UTC, Walter Bright wrote:
> On 7/28/2019 5:48 AM, Exil wrote:
>> You get an ICE with optlink instead of "Error: Out of Memory".
>
> The error Ethan reported wasn't coming from the linker.

Sigh. The problem isn't with what was currently being compiled (kind of obvious). The problem is that the "official" DMD executable is compiled with optlink. Sorry I wasn't clear enough in my first post, I thought it was obvious.

On Sunday, 28 July 2019 at 21:33:57 UTC, Walter Bright wrote:
> Dustmite is not a good tool for out of memory errors, because the error can disappear whenever anything is removed from the code.

#!/bin/sh
set -e
ulimit -v 1000000
dmd test.d 2>&1 |grep "out of memory"

The main problem you'll run into is dustmite removing a load bearing element of the error and turning one OOM into another OOM. This can be partially mitigated by running dmd with "-v" and grepping for the last line in the ordinary failing dmd output, to ensure it gets "at least that far."

Dustmite is not a magical cure-all. Like any tool, it needs some investment of effort to use it fully, and there's tasks it's less good at. But reducing ooms with dustmite is certainly possible.