[Issue 20276] New: DMD v2.088.0 Compile with dub fails due to an illegal instruction

d-bugmail at puremagic.com d-bugmail at puremagic.com
Mon Oct 7 09:17:51 UTC 2019


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

          Issue ID: 20276
           Summary: DMD v2.088.0 Compile with dub fails due to an illegal
                    instruction
           Product: D
           Version: D2
          Hardware: x86_64
                OS: Windows
            Status: NEW
          Severity: critical
          Priority: P1
         Component: dmd
          Assignee: nobody at puremagic.com
          Reporter: dougclayton4231 at hotmail.com

Created attachment 1763
  --> https://issues.dlang.org/attachment.cgi?id=1763&action=edit
DirectX Binding code

Hi,

I've had no problems compiling my project with DMD v2.087.0 but after upgrading
to DMD v2.088.0, I get this error:

> Executing task in folder HurricaneEngine: dub build --build=debug <

Performing "debug" build using C:\D\dmd2\windows\bin\dmd.exe for x86_64.
hurricane ~master: building configuration "application"...
---
ERROR: This is a compiler bug.
Please report it via https://issues.dlang.org/enter_bug.cgi
with, preferably, a reduced, reproducible example and the information below.
DustMite (https://github.com/CyberShadow/DustMite/wiki) can help with the
reduction.
---
DMD v2.088.0-dirty
predefs   Have_hurricane DigitalMars Windows CRuntime_Microsoft
CppRuntime_Microsoft LittleEndian D_Version2 all D_SIMD D_InlineAsm_X86_64
X86_64 Win64 D_LP64 assert D_ModuleInfo D_Exceptions D_TypeInfo D_HardFloat
binary    C:\D\dmd2\windows\bin\dmd.exe
version   v2.088.0-dirty
config    C:\D\dmd2\windows\bin\sc.ini
DFLAGS    -IC:\D\dmd2\windows\bin\..\..\src\phobos
-IC:\D\dmd2\windows\bin\..\..\src\druntime\import -L/OPT:NOICF
---

object.Error@(0): Illegal Instruction
----------------
0x00629442
C:\D\dmd2\windows\bin\dmd.exe failed with exit code 1.
The terminal process terminated with exit code: 2

I use Visual Studio code to run my compiles, but it seems like my bindings to
the DirectX API are causing it. Can someone take a look?

--


More information about the Digitalmars-d-bugs mailing list