I've verified that the upstream binary distribution (http://llvm.org/releases/3.5.0/clang+llvm-3.5.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz) is *not* affected by this bug.
@RJVB: all I know is that rL201729 was considered for inclusion in clang-3.4.1, which I believe predates 3.5.0. But I'm not intimately familiar with the branching/merging process of clang, so I cannot be sure about this.
I've verified that the upstream binary distribution (http:// llvm.org/ releases/ 3.5.0/clang+ llvm-3. 5.0-x86_ 64-linux- gnu-ubuntu- 14.04.tar. xz) is *not* affected by this bug.
@RJVB: all I know is that rL201729 was considered for inclusion in clang-3.4.1, which I believe predates 3.5.0. But I'm not intimately familiar with the branching/merging process of clang, so I cannot be sure about this.