[llvm] r210814 - CodeGen: enable mov.w/mov.t pairs with minsize for WoA

[Tim Northover]

> +    // NOTE Windows on ARM needs to use mov.w/mov.t pairs to materialise 32-bit
> +    // immediates as it is inherently position independent, and may be out of
> +    // range otherwise.

What does "inherently position independent" mean here? Because I can
see no way in which the fragment you're testing could be loaded at an
arbitrary address without runtime fixup.

And if you are relying on runtime fixup, "inherently
position-dependent" would probably be a better description.

Cheers.

Tim.