[cfe-dev] choosing the gcc toolchain

[reed kotler]

Okay. I'm rerunning the build and specifying mips32.

I will need to work out this whole test matrix of big endian/little 
endian and mips32/mips64 and make sure
we have them all covered in the build bots.

We can build some additional tool chains for mips64 and gcc 4.7

On 03/03/2014 07:27 AM, Simon Atanasyan wrote:
> On Mon, Mar 3, 2014 at 7:15 PM, reed kotler <rkotler at mips.com> wrote:
>> rkotler at mipsswbrd006-le:~/caviumnativellvm/build$
>> ./Release+Asserts/bin/clang++ -v
>> clang version 3.5 (gitosis at dmz-portal.mips.com:clang.git
>> f4481e0e412e3f817e65d5ce1c835381dc7a7773)
>> (gitosis at dmz-portal.mips.com:llvm.git
>> 18fe44cb057e4b11533bd3f814b96fdca724baf0)
>> Target: mips64el-unknown-linux-gnu
> [...]
>
>> rkotler at mipsswbrd006-le:~/caviumnativellvm/build$  find /usr/lib -name
>> crtbegin.o
>> /usr/lib/gcc/mipsel-linux-gnu/4.7/crtbegin.o
>> /usr/lib/gcc/mipsel-linux-gnu/4.6/64/crtbegin.o
> That is why the clang selects toolchain version 4.6. You provide
> "mips64el-unknown-linux-gnu" triple but toolchain version 4.7 does not
> support 64 ABI. So the clang fall back to the 4.6.
>
> The first time you provide "mipsel-unknown-linux-gnu" triple and the
> fixed clang successfully selects toolchain version 4.7.
>