Bug 19290 – immutable associative array corruption with -m64 and MinGW

It seems that a kind of corruption happens in dparse when it's compiled with -m64, lld linker and MinGW. To reproduce save this code in a bat and run it from a console: ``` git clone https://github.com/dlang-community/libdparse.git git clone https://github.com/dlang-community/stdx-allocator.git cd libdparse git checkout v0.9.9 cd .. dmd main.d ^ libdparse\src\std\experimental\lexer.d ^ libdparse\src\dparse\ast.d ^ libdparse\src\dparse\lexer.d ^ libdparse\src\dparse\parser.d ^ libdparse\src\dparse\rollback_allocator.d ^ libdparse\src\dparse\stack_buffer.d ^ stdx-allocator\source\stdx\allocator\package.d ^ stdx-allocator\source\stdx\allocator\mallocator.d ^ stdx-allocator\source\stdx\allocator\gc_allocator.d ^ -Ilibdparse\src -Istdx-allocator\source -m64 -debug main.exe ``` Which gives a range error that didn't happen when using -m32, here : https://github.com/dlang-community/libdparse/blob/95444a966923a24098c31464e09a7096208da155/src/dparse/ast.d#L88 This really shouldn't happen since each possible entry is setup in a static module constructor just above. The problem doesn't happen if the involved assoc array is not immutable, which will be used as workaround for now. (test case wont be affected)

main.d for the reproduction ``` void main() { import dparse.parser, dparse.ast, dparse.lexer, dparse.rollback_allocator; import std.file; class Visitor : ASTVisitor {} LexerConfig config; StringCache cache = StringCache(16); RollbackAllocator rba; auto src = readText(r"libdparse\src\dparse\parser.d"); auto tok = getTokensForParser(src, config, &cache); auto mod = parseModule(tok, "stdin", &rba); auto vis = new Visitor; vis.visit(mod); } ```

problem is gone since DMD 2.084