How to track down a bad llvm optimization pass

[Joakim via digitalmars-d-ldc]

On Saturday, 18 June 2016 at 15:31:03 UTC, Joakim wrote:
> On Friday, 17 June 2016 at 08:48:01 UTC, David Nadlinger wrote:
>> I just tried both triples with ldc master of a week ago and 
>> llvm-3.6.2. IR for each is identical except gnueabihf has 
>> stuff for shared lib setup (dso_ctor, etc) which is not in 
>> android version.
>
> I'll try building and linking against llvm 3.6 and 3.7 and see 
> if it makes a difference.

I just built and linked against llvm 3.7.1 and the problem goes 
away, so it appears that it is a regression in the GVN 
optimization pass with llvm 3.8.0.  I'll check if it goes away 
with llvm master, and file an llvm bug if it doesn't.