On Tue, 2014-10-28 at 14:06 -0700, Matthew Fortune wrote:
> While the patch could be fixed to account for all of this we need to
> determine if the case which won't work is the exact one which is needed
> (and I believe it is). I.e. Android applications for MIPS are MIPS32r1
> O32 FP32 NAN1985 cur
Matthew Fortune writes:
> > >> > Do you have an objection to allowing an option to disable these
> > >> instructions (despite the reason for wanting to do so)?
> > >>
> > >> Yes this seems like a bad workaround for broken code.
> > >>
> > > Well, we work around broken hardware all the time. Wha
On Tue, Oct 28, 2014 at 11:46 AM, Matthew Fortune
wrote:
>> >> > Do you have an objection to allowing an option to disable these
>> >> instructions (despite the reason for wanting to do so)?
>> >>
>> >> Yes this seems like a bad workaround for broken code.
>> >>
>> > Well, we work around broken
> >> > Do you have an objection to allowing an option to disable these
> >> instructions (despite the reason for wanting to do so)?
> >>
> >> Yes this seems like a bad workaround for broken code.
> >>
> > Well, we work around broken hardware all the time. What would you
> suggest that Steve do i
il.com]
>> >> Sent: Monday, October 27, 2014 6:32 PM
>> >> To: Steve Ellcey
>> >> Cc: Moore, Catherine; Matthew Fortune; GCC Patches
>> >> Subject: Re: [Patch] Add MIPS flag to avoid use of
>> >> ldc1/sdc1/ldxc1/sdxc1
>> >>
>>
> -Original Message-
> From: Andrew Pinski [mailto:pins...@gmail.com]
> Sent: Monday, October 27, 2014 6:41 PM
> To: Moore, Catherine
> Cc: Steve Ellcey; Matthew Fortune; GCC Patches
> Subject: Re: [Patch] Add MIPS flag to avoid use of ldc1/sdc1/ldxc1/sdxc1
>
> O
New command-line options need documenting in invoke.texi.
--
Joseph S. Myers
jos...@codesourcery.com
> Subject: Re: [Patch] Add MIPS flag to avoid use of ldc1/sdc1/ldxc1/sdxc1
>>
>> On Mon, Oct 27, 2014 at 3:23 PM, Steve Ellcey wrote:
>> >
>> > There are some MIPS patches that have been applied to the Google
>> > Android GCC tree but not been submitted to
On Mon, 2014-10-27 at 15:32 -0700, Andrew Pinski wrote:
> On Mon, Oct 27, 2014 at 3:23 PM, Steve Ellcey wrote:
> >
> > There are some MIPS patches that have been applied to the Google Android GCC
> > tree but not been submitted to FSF GCC. I would like to get those patches
> > checked in if possi
> -Original Message-
> From: Andrew Pinski [mailto:pins...@gmail.com]
> Sent: Monday, October 27, 2014 6:32 PM
> To: Steve Ellcey
> Cc: Moore, Catherine; Matthew Fortune; GCC Patches
> Subject: Re: [Patch] Add MIPS flag to avoid use of ldc1/sdc1/ldxc1/sdxc1
>
> O
On Mon, Oct 27, 2014 at 3:23 PM, Steve Ellcey wrote:
>
> There are some MIPS patches that have been applied to the Google Android GCC
> tree but not been submitted to FSF GCC. I would like to get those patches
> checked in if possible. The first one is to add a new MIPS flag to turn
> off the u
There are some MIPS patches that have been applied to the Google Android GCC
tree but not been submitted to FSF GCC. I would like to get those patches
checked in if possible. The first one is to add a new MIPS flag to turn
off the use of ldc1/sdc1/ldxc1/sdxc1. Google Earth has a custom allocat
12 matches
Mail list logo
