[llvm-commits] [llvm] r157884 - in /llvm/trunk: include/llvm/Instructions.h include/llvm/Support/IntegersSubset.h include/llvm/Support/IntegersSubsetMapping.h lib/Bitcode/Writer/BitcodeWriter.cpp lib/CodeGen/SelectionDAG/SelectionDAGBuilder.cpp l

[Stepan Dyatkovskiy]

That's interesting. Looks like compiler bug.
 If I'm get right on stage 2 you use gcc for clang building. And on stage 3 you use clang for clang building. And gcc produces binaries that are differs from binaries produced by clang, right?
And all is fixed after you add IntRange copy constructor.

> Would <class IntType> be POD always?
Not. It will APInt-based types always. And APInt is pod only if its bitwidth <= 64.

-Stepan.

04.06.2012, 02:55, "NAKAMURA Takumi" <geek4civic at gmail.com>:
> 2012/6/4 Stepan Dyatkovskiy <stpworld at narod.ru>:
>
>>  Did you got any failures or warnings after I removed it?
>
> It caused instability between stage 2 (gcc-built clang) and stage 3
> (clang-built clang).
>
> http://bb.pgr.jp/builders/clang-3stage-x86_64-linux/builds/1/steps/compare_23/logs/stdio
>
> ...Takumi