64bit DMD on Windows

[H. S. Teoh]

On Fri, Jun 29, 2018 at 11:41:41PM +0000, SonicFreak94 via Digitalmars-d wrote:
> On Friday, 29 June 2018 at 20:57:24 UTC, Jonathan M Davis wrote:
> > [...]
> > It could be fixed, even if it's just adding a compiler switch to
> > indicate that you want it to use the GC to collect memory, because
> > you're going to run out of memory if you don't. As I understand it,
> > the compiler already can have that turned on internally. It's just
> > that it hurt compilation times enough to do so that it's been left
> > off - which makes sense for many, many cases, but is a definite
> > problem when your project is large enough or doing enough CTFE that
> > compiling it causes it to run out of memory.

This has been a showstopper for me on low-memory machines. If I hadn't
been using a high-memory system when I first tried out D, I might have
just walked away.

This *needs* to be an option.

Though the last time I tried compiling DMD with the GC enabled, it
segfaulted on me, so there may be bugs that need to be fixed in order
for this to work.


[...]
> I managed to get around this issue by using LDC to compile a test
> project, but the memory usage was insane. It used more than 4GB of
> memory. I would rather have slower compile times, personally. I bet
> letting the GC do its job and free memory is less time consuming than
> letting the compiler eventually run out of memory, halt, and leave me
> to scramble to free up system memory so that I can try again.

Absolutely agree.  As I said, this issue has been a showstopper for me
on low-memory machines; it basically makes D unusable. (And one of the
environments I was trying to use dmd in is a remote colocated server for
which adding additional memory is not a practical option.)


T

-- 
It only takes one twig to burn down a forest.