LDC generate assembly unused instructions.

[David Nadlinger]

On 2 Apr 2018, at 17:36, SrMordred via digitalmars-d-ldc wrote:
> Why LDC keep unused assembly code like
> 'example.Int.__mixin2.toHash' or 'example.Int.__mixin2.opBinary'
> on the binary?

In short, there is no way for the compiler to know whether they might be 
used from another module (object file).

They should disappear in the final executable on Linux (and I believe 
also Windows), though, if the linker does its job (--gc-sections).

  —David