All of lore.kernel.org
 help / color / mirror / Atom feed
From: steve.mcintyre@linaro.org (Steve McIntyre)
To: linux-arm-kernel@lists.infradead.org
Subject: Removal of NWFPE in its entirety, and VFP emulation code
Date: Wed, 10 Apr 2013 19:24:15 +0100	[thread overview]
Message-ID: <20130410182415.GD19224@einval.com> (raw)
In-Reply-To: <alpine.LFD.2.03.1304101307280.17375@syhkavp.arg>

On Wed, Apr 10, 2013 at 01:30:35PM -0400, Nicolas Pitre wrote:
>On Wed, 10 Apr 2013, Russell King - ARM Linux wrote:
>
>> I have just committed a patch to remove the arch/arm/nwfpe code from
>> the kernel, and the VFP code emulating the FP operations.
>> 
>> This I have done after it has been brought to my attention by the OSADL's
>> GPL-violations project that the license for the softfloat library is
>> incompatible with GPLv2.  This is because the FSF have ruled that
>> indemnification clauses consitute an "additional restriction" which is
>> incompatible with the GPLv2 section 6.  NWFPE contains the softfloat
>> library, and VFP's emulation code is a derivative of softfloat.
>> 
>> This will be very disruptive for ARMv4 and ARMv5 CPUs, which will no
>> longer be able to run userspace with NWFPE support removed.  A possible
>> solution there is to resurrect FASTFPE support and merge that into
>> mainline in place of NWFPE.  FASTFPE's hooks are all present in the
>> kernel, and it should just be a case of adding the FASTFPE code.
>> However, FASTFPE is probably lacking GDB and signal stack support.
>> (FastFPE's per-thread workspace is different from NWFPE.)
>
>A point worth mentioning is the EABI availability since 2006 which moved 
>away from FPA completely. A soft-float library in user space is used in 
>that case.  Major ARM binary producers including all ARM distros moved 
>to EABI with user space soft-float since then as it is order of 
>magnitude faster than FPA emulation.  So 99.99% of ARMv4 and ARMv5 users 
>are unlikely to be affected.
>
>So another option here might imply deprecating OABI support entirely, 
>given that it is useless without FPA and people keeping current with the 
>latest kernel are very likely to already use EABI user space.

Plus, OABI is just about dead in major places like glibc too.

Cheers,
-- 
Steve McIntyre                                steve.mcintyre at linaro.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs

  reply	other threads:[~2013-04-10 18:24 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10 10:40 Removal of NWFPE in its entirety, and VFP emulation code Russell King - ARM Linux
2013-04-10 11:18 ` Måns Rullgård
2013-04-10 11:42   ` Russell King - ARM Linux
2013-04-10 11:58     ` Måns Rullgård
2013-04-10 18:54       ` Russell King - ARM Linux
2013-04-10 19:23         ` Måns Rullgård
2013-04-10 20:03           ` Russell King - ARM Linux
2013-04-10 20:46             ` Måns Rullgård
2013-04-10 21:04               ` Russell King - ARM Linux
2013-04-10 21:18                 ` Måns Rullgård
2013-04-10 21:29                   ` Nicolas Pitre
2013-04-10 21:39                     ` Måns Rullgård
2013-04-10 21:45                   ` Russell King - ARM Linux
2013-04-10 22:21                     ` Måns Rullgård
2013-04-10 23:19                       ` Nicolas Pitre
2013-04-10 13:21 ` Will Deacon
2013-04-10 19:15   ` Russell King - ARM Linux
2013-04-10 17:30 ` Nicolas Pitre
2013-04-10 18:24   ` Steve McIntyre [this message]
2013-04-10 18:55   ` Russell King - ARM Linux
2013-04-10 18:58     ` Nicolas Pitre
2013-04-10 19:02       ` Russell King - ARM Linux
2013-04-11 18:37         ` Imre Kaloz
2013-04-10 19:00   ` Aaro Koskinen
2013-04-10 19:03     ` Nicolas Pitre
2013-04-10 19:06     ` Russell King - ARM Linux
2013-04-10 19:19       ` Nicolas Pitre
2013-04-10 19:25   ` Måns Rullgård
2013-04-10 20:04     ` Russell King - ARM Linux
2013-04-10 18:38 ` jonsmirl at gmail.com
2013-04-10 19:12   ` Russell King - ARM Linux
2013-04-10 21:46 ` Russell King - ARM Linux
2013-04-18 13:31 ` Russell King - ARM Linux

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130410182415.GD19224@einval.com \
    --to=steve.mcintyre@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.