lows.
>>> 1. mips-linux-gnu
>>> 2. mips-linux-gnu --enable-targets=all
>>> 3. mips64-linux-gnu
>>>
>>> These targets are affected by this MIPS Android patch.
>>>
>>> Then, I checked the output from "gcc -dumpspecs" before and
>> 3. mips64-linux-gnu
>>
>> These targets are affected by this MIPS Android patch.
>>
>> Then, I checked the output from "gcc -dumpspecs" before and after applying
>> the patch.
>> The specs have 6 places of differences for Android due to
Richard Sandiford wrote:
> > Index: gcc/config/mips/gnu-user.h
> > ===
> > --- gcc/config/mips/gnu-user.h (revision 186580)
> > +++ gcc/config/mips/gnu-user.h (working copy)
> > @@ -45,8 +45,10 @@
> > /* A standard GNU/Linu
On 20/04/2012, at 1:34 PM, Fu, Chao-Ying wrote:
> Hi Maxim, Richard,
>
> I built cross-toolchains for 3 different targets as follows.
> 1. mips-linux-gnu
> 2. mips-linux-gnu --enable-targets=all
> 3. mips64-linux-gnu
>
> These targets are affected by this MIPS Andr
"Fu, Chao-Ying" writes:
> Index: gcc/config/mips/gnu-user.h
> ===
> --- gcc/config/mips/gnu-user.h(revision 186580)
> +++ gcc/config/mips/gnu-user.h(working copy)
> @@ -45,8 +45,10 @@
> /* A standard GNU/Linux mapping
Hi Maxim, Richard,
I built cross-toolchains for 3 different targets as follows.
1. mips-linux-gnu
2. mips-linux-gnu --enable-targets=all
3. mips64-linux-gnu
These targets are affected by this MIPS Android patch.
Then, I checked the output from "gcc -dumpspecs" before and afte