extern (C++) problems

[TurkeyMan]

I'm getting a whole lot of

Assertion failed: !(Pair.first != Ty && Pair.second == Ty) && "mapping to a source type", file D:\OpenSource\LLVM\llvm-git\lib\Linker\LinkModules.cpp, line 264

When I try and use extern (C++)

Are these known, or shall I start contriving cases?

[TurkeyMan]

Actually, upon deep inspection, it's something rather more sinister... it's gonna be a lot of work to simplify a case >_<

[redstar]

Are you using ldmd2 or option -singleobj? Which ldc/LLVM version?

[TurkeyMan]

I think VisualD invokes ldc2. I'm using the latest MSVC LDC build (ldc2-0.15.2-beta1-win64-msvc)

I've fixed other related problems, and after doing so, it seems this problem has gone away.
It was hard to isolate the particular thing causing this ICE without fixing numerous other things that seem to have collectively stopped this one.

[TurkeyMan]

This problem keeps coming and going. It seems to appear upon a whole suite of different problems. It must be a catch-all at the end of line somewhere, after other checks fail to catch the error.

The common thread among my problems is that I'm using extern(C++) extensively.

[redstar]

I am closing this issue because it is a duplicate of #855 and #921. It is really an LLVM bug, see #904.
It has nothing to do with catch-all clauses. It is caused by -singleobj which is passed to ldc2 by ldmd2.

[TurkeyMan]

I don't use -singleobj though. I do all-at-once builds :/

[dnadlinger]

With ldmd2 or ldc2?

[TurkeyMan]

@rainers ?
I suspect ldc2...

[rainers]

Yes, Visual D calls ldc2 directly, and it doesn't use -singleobj.