I'm planning to write a few functions purely in x86 Assembly (later adding ARM and other platforms), and I'm planning to support both DMD and LDC. As I'm running into massive issues when compiling and running very long assembly codes in LDC (see this: https://github.com/ZILtoid1991/CPUblit/blob/master/src/CPUblit/composing.d), I came up with the solution of using an external assembler like NASM, then add its build commands to DUB's prebuild commands. Should I go with C or D API for function calls? Or issue a D improvement proposal on fixing the SIMD support?

On 25 Apr 2018, at 16:57, solidstate1991 via digitalmars-d-ldc wrote:
> very long assembly codes in LDC (see this: https://github.com/ZILtoid1991/CPUblit/blob/master/src/CPUblit/composing.d)

As far as weird corner cases go, this doesn't really qualify as "very long" yet – perhaps we could fix these issues?

 – David

On Thursday, 26 April 2018 at 13:14:15 UTC, David Nadlinger wrote:
> On 25 Apr 2018, at 16:57, solidstate1991 via digitalmars-d-ldc wrote:
>> very long assembly codes in LDC (see this: https://github.com/ZILtoid1991/CPUblit/blob/master/src/CPUblit/composing.d)
>
> As far as weird corner cases go, this doesn't really qualify as "very long" yet – perhaps we could fix these issues?
>
>  – David

It looks like a single issue, potentially trivially to fix. I already told him to create a new issue with reduced testcase: https://github.com/ldc-developers/ldc/issues/2629#issuecomment-383669844

On Thursday, 26 April 2018 at 13:54:05 UTC, kinke wrote:
> It looks like a single issue, potentially trivially to fix. I already told him to create a new issue with reduced testcase: https://github.com/ldc-developers/ldc/issues/2629#issuecomment-383669844

Yep – I created this: https://github.com/ldc-developers/ldc/issues/2667

 — David