A bit disappointing that it just ends at "we have this magic compiler bug that was magically fixed in the next version" without any attempt to find the cause (e.g. by bisecting Clang). How can you know that it was really fixed and isn't just hiding until something unrelated in the codebase moves around again?
I agree, but I guess the original quest went already too deep into the rabbit hole and he wanted to escape as soon as possible (after 2 years!). It looks like an interesting project, and if someone can track the exact commit, then can farm some karma here with a nice blog post.
