Thread overview
msgpack-d 0.9.3 unittest fails
Feb 11, 2015
drug
Feb 13, 2015
David Nadlinger
Feb 16, 2015
drug
Feb 17, 2015
Kai Nacke
February 11, 2015
this command:
drug@astra:~/.dub/packages/msgpack-d-0.9.3$ dub --build=unittest --compiler=ldmd2

fails with the result:

The determined compiler type "ldc" doesn't match the expected type "dmd". This will probably result in build errors.
Building msgpack-d 0.9.3 configuration "library", build type unittest.
Running ldmd2...
Stored value type does not match pointer operand type!
  store [2 x i8]* %18, [2 x i8]* %22, !dbg !10792
 [2 x i8]Stored value type does not match pointer operand type!
  store [2 x i8]* %23, [2 x i8]* %27, !dbg !10792
 [2 x i8]LLVM ERROR: Broken function found, compilation aborted!
FAIL .dub/build/library-unittest-linux.posix-x86_64-ldc_2066-28222C70EA831B74411B8A9C9233AD02/ msgpack-d staticLibrary
Error executing command run:
ldmd2 failed with exit code 1.

Don't know where to file this issue, do it here so far.

Compiler version is:

drug@astra:~/.dub/packages/msgpack-d-0.9.3$ ldmd2
LDC - the LLVM D compiler (0.15.0):
  based on DMD v2.066.1 and LLVM 3.5.0
  Default target: x86_64-pc-linux-gnu
  Host CPU: core-avx-i
February 13, 2015
On 11 Feb 2015, at 13:31, drug via digitalmars-d-ldc wrote:
> Don't know where to file this issue, do it here so far.

Any LLVM ERRORs are definitely bugs in LDC. It would be great if you could add an issue to the tracker: https://github.com/ldc-developers/ldc/issues

Thanks,
David
February 16, 2015
On 14.02.2015 01:50, David Nadlinger via digitalmars-d-ldc wrote:
>
> Any LLVM ERRORs are definitely bugs in LDC. It would be great if you
> could add an issue to the tracker:
> https://github.com/ldc-developers/ldc/issues
>
> Thanks,
> David

Done https://github.com/ldc-developers/ldc/issues/841
February 17, 2015
On Monday, 16 February 2015 at 10:14:37 UTC, drug wrote:
> On 14.02.2015 01:50, David Nadlinger via digitalmars-d-ldc wrote:
>>
>> Any LLVM ERRORs are definitely bugs in LDC. It would be great if you
>> could add an issue to the tracker:
>> https://github.com/ldc-developers/ldc/issues
>>
>> Thanks,
>> David
>
> Done https://github.com/ldc-developers/ldc/issues/841

Thanks!

Regards,
Kai