Maxim Kuvyrkov wrote:
> I encourage you to submit the MIPS Android patches to
> gcc-patches@. And, as long as your changes preserve the
> status quo of mips-*-* being big-endian by default and
> mipsel-*-* being little-endian by default, there should be no
> major obstacles to merge those in.
On 4/04/2012, at 6:28 AM, Fu, Chao-Ying wrote:
> Andrew Pinski wrote:
>> The point is mips*-*-* is big endian and mipsel*-*-* is little endian.
>> And doing adding a target which says mips-linux-android which is
>> little-endian is just backwards. Is there anyway to fix the target
>> triplet to b
Andrew Pinski wrote:
> The point is mips*-*-* is big endian and mipsel*-*-* is little endian.
> And doing adding a target which says mips-linux-android which is
> little-endian is just backwards. Is there anyway to fix the target
> triplet to be mipsel-linux-android including inside the official
On Tue, Apr 3, 2012 at 10:45 AM, Fu, Chao-Ying wrote:
> Andrew Pinski wrote:
>
>> On Mon, Apr 2, 2012 at 1:55 PM, Fu, Chao-Ying wrote:
>> > It basically sets the MIPS target to little-endian MIPS32
>> for mips-linux-android.
>>
>> That seems broken because mips-*-* is big-endian and mipsel-*-* i
Andrew Pinski wrote:
> On Mon, Apr 2, 2012 at 1:55 PM, Fu, Chao-Ying wrote:
> > It basically sets the MIPS target to little-endian MIPS32
> for mips-linux-android.
>
> That seems broken because mips-*-* is big-endian and mipsel-*-* is
> little-endian. Is any way of fixing that before even try
On Mon, Apr 2, 2012 at 1:55 PM, Fu, Chao-Ying wrote:
> It basically sets the MIPS target to little-endian MIPS32 for
> mips-linux-android.
That seems broken because mips-*-* is big-endian and mipsel-*-* is
little-endian. Is any way of fixing that before even trying to
submitting the patch? Be
Richard Sandiford wrote:
> Sent: Monday, April 02, 2012 11:45 AM
> To: Maxim Kuvyrkov
> Cc: Richard Earnshaw; Jan Hubicka; gcc@gcc.gnu.org
> Subject: Re: [GCC Steering Committee] Android sub-port reviewer
>
> Maxim Kuvyrkov writes:
> > On 29/03/2012, at 5:38 PM, Maxim Ku
Maxim Kuvyrkov writes:
> On 29/03/2012, at 5:38 PM, Maxim Kuvyrkov wrote:
>
>> I volunteer as the reviewer for Android sub-port.
>>
>> Android/Bionic support is an extension over Linux port and is being
>> gradually added for more and more architectures. I wrote the original
>> Android GCC sup
On 01/04/12 20:57, Maxim Kuvyrkov wrote:
> On 29/03/2012, at 5:38 PM, Maxim Kuvyrkov wrote:
>
>> I volunteer as the reviewer for Android sub-port.
>>
>> Android/Bionic support is an extension over Linux port and is being
>> gradually added for more and more architectures. I wrote the original
>
> On 29/03/2012, at 5:38 PM, Maxim Kuvyrkov wrote:
>
> > I volunteer as the reviewer for Android sub-port.
> >
> > Android/Bionic support is an extension over Linux port and is being
> > gradually added for more and more architectures. I wrote the original
> > Android GCC support for ARM (unde
On 29/03/2012, at 5:38 PM, Maxim Kuvyrkov wrote:
> I volunteer as the reviewer for Android sub-port.
>
> Android/Bionic support is an extension over Linux port and is being gradually
> added for more and more architectures. I wrote the original Android GCC
> support for ARM (under a watchful d
I volunteer as the reviewer for Android sub-port.
Android/Bionic support is an extension over Linux port and is being gradually
added for more and more architectures. I wrote the original Android GCC
support for ARM (under a watchful design eye of Joseph Myers), and know how the
bits fit toget
12 matches
Mail list logo
