Re: Deprecating ARM FPA support (was: ARM Neon Tests Failing on non-Neon Target)

2010-07-13 Thread Paul Brook
> However, although no one currently sells FPA hardware, it is widely > supported as the only floating point model emulated by the Linux > kernel, and people have to use it when compiling stuff to run on OABI > systems, which include boards currently on the market based on ARMv4 > (no t) such as th

Re: Deprecating ARM FPA support (was: ARM Neon Tests Failing on non-Neon Target)

2010-06-28 Thread Richard Earnshaw
On Mon, 2010-06-28 at 01:37 +0100, Martin Guy wrote: > On 6/27/10, Gerald Pfeifer wrote: > > On Mon, 24 May 2010, Richard Kenner wrote: > > > I think that's a critical distinction. I can't see removing a port just > > > because it's not used much (or at all) because it might be valuable for >

Re: Deprecating ARM FPA support (was: ARM Neon Tests Failing on non-Neon Target)

2010-06-27 Thread Martin Guy
On 6/27/10, Gerald Pfeifer wrote: > On Mon, 24 May 2010, Richard Kenner wrote: > > I think that's a critical distinction. I can't see removing a port just > > because it's not used much (or at all) because it might be valuable for > > historical reason or to show examples for how to do things.

Re: Deprecating ARM FPA support (was: ARM Neon Tests Failing on non-Neon Target)

2010-06-27 Thread Gerald Pfeifer
On Mon, 24 May 2010, Richard Kenner wrote: > I think that's a critical distinction. I can't see removing a port just > because it's not used much (or at all) because it might be valuable for > historical reason or to show examples for how to do things. If the > maintenance burden of keeping tha

Re: Deprecating ARM FPA support (was: ARM Neon Tests Failing on non-Neon Target)

2010-05-24 Thread Richard Kenner
> What's different is that there is a well-maintained arm-eabi port. The > arm-elf port and all its legacy just gets in the way. > > The vax back-end only affects VAX; likewise for the PDP11 port. I think that's a critical distinction. I can't see removing a port just because it's not used much

Re: Deprecating ARM FPA support (was: ARM Neon Tests Failing on non-Neon Target)

2010-05-24 Thread Richard Earnshaw
On Mon, 2010-05-24 at 11:33 +, Joseph S. Myers wrote: > (I've CC:ed the listed GCC maintainers for various OS ports whose ARM > configurations in GCC do not appear to be using EABI, as well as Pedro for > WinCE, given the discussions of deprecation.) Deprecations are generally > a matter f

Re: Deprecating ARM FPA support (was: ARM Neon Tests Failing on non-Neon Target)

2010-05-24 Thread Joseph S. Myers
On Mon, 24 May 2010, Steven Bosscher wrote: > > The vax back-end only affects VAX; likewise for the PDP11 port. > > ...all this legacy just gets in the way of gcc as a whole. So I still > don't see the difference. > > Nb, I don't oppose deprecating any arm stuff, but I just would like to > know

Re: Deprecating ARM FPA support (was: ARM Neon Tests Failing on non-Neon Target)

2010-05-24 Thread Joseph S. Myers
(I've CC:ed the listed GCC maintainers for various OS ports whose ARM configurations in GCC do not appear to be using EABI, as well as Pedro for WinCE, given the discussions of deprecation.) Deprecations are generally a matter for the relevant maintainers, which in this case means target maint

Re: Deprecating ARM FPA support (was: ARM Neon Tests Failing on non-Neon Target)

2010-05-24 Thread Richard Earnshaw
On Mon, 2010-05-24 at 12:42 +0200, Steven Bosscher wrote: > On 5/24/10, Richard Earnshaw wrote: > > > > On Sun, 2010-05-23 at 23:15 +0200, Steven Bosscher wrote: > >> On Sun, May 23, 2010 at 10:27 PM, Mark Mitchell > >> wrote: > >> > Martin Guy wrote: > >> > > >> >> Dropping FPA support from GCC

Re: Deprecating ARM FPA support (was: ARM Neon Tests Failing on non-Neon Target)

2010-05-24 Thread Steven Bosscher
On 5/24/10, Richard Earnshaw wrote: > > On Sun, 2010-05-23 at 23:15 +0200, Steven Bosscher wrote: >> On Sun, May 23, 2010 at 10:27 PM, Mark Mitchell >> wrote: >> > Martin Guy wrote: >> > >> >> Dropping FPA support from GCC effectively makes the OABI unusable, and >> >> often we are forced to use

Re: Deprecating ARM FPA support (was: ARM Neon Tests Failing on non-Neon Target)

2010-05-24 Thread Richard Earnshaw
On Sun, 2010-05-23 at 23:15 +0200, Steven Bosscher wrote: > On Sun, May 23, 2010 at 10:27 PM, Mark Mitchell wrote: > > Martin Guy wrote: > > > >> Dropping FPA support from GCC effectively makes the OABI unusable, and > >> often we are forced to use that by the environment supplied to us. Are > >>

Re: Deprecating ARM FPA support (was: ARM Neon Tests Failing on non-Neon Target)

2010-05-24 Thread Richard Earnshaw
On Sun, 2010-05-23 at 05:11 +0100, Martin Guy wrote: > On 5/11/10, Mark Mitchell wrote: > > Richard Earnshaw wrote: > > > > > Speaking of which, we should probably formally deprecate the old arm-elf > > > derived targets in 4.6 so that we can remove them in 4.7. > > > > > Similarly, we should

Re: Deprecating ARM FPA support (was: ARM Neon Tests Failing on non-Neon Target)

2010-05-23 Thread Steven Bosscher
On Sun, May 23, 2010 at 10:27 PM, Mark Mitchell wrote: > Martin Guy wrote: > >> Dropping FPA support from GCC effectively makes the OABI unusable, and >> often we are forced to use that by the environment supplied to us. Are >> there significant advantages to removing FPA support, other than >> re

Re: Deprecating ARM FPA support (was: ARM Neon Tests Failing on non-Neon Target)

2010-05-23 Thread Mark Mitchell
Martin Guy wrote: > Dropping FPA support from GCC effectively makes the OABI unusable, and > often we are forced to use that by the environment supplied to us. Are > there significant advantages to removing FPA support, other than > reducing the size of the ARM backend? I think that maintainabili

Deprecating ARM FPA support (was: ARM Neon Tests Failing on non-Neon Target)

2010-05-22 Thread Martin Guy
On 5/11/10, Mark Mitchell wrote: > Richard Earnshaw wrote: > > > Speaking of which, we should probably formally deprecate the old arm-elf > > derived targets in 4.6 so that we can remove them in 4.7. > > > Similarly, we should deprecate support for the FPA on ARM. > > I agree. No one seems to