old libraries

People only started seriously getting rid of swp around ~2010 when gas started emitting a warning about it (and compiling to thumb2 become more common). People using old libraries (like boost 1.49*) in their projects are still hitting it:

http://www.rtsoft.com/forums/showthread.php?16636-Warning...

Take an ignorant developer who uses and old copy of a library and doesn't care about warnings... they might still be uploading new packages to play store with swp.

This needs to be attacked from multiple fronts:

- change gas to emit an error instead of warning on swp from armv7+
- get the gas patch into android NDK
- error on deprecated instructions on play store uploads
- spam developers of existing apps in play store about their use of deprecated instructions?
- emulate swp until google reports that there is less than X apps in play store without swp.

Just emulating in kernel won't solve the issue, but it still needs to be done - OEM's will do it anyways, and not having it mainline will be seen from OEM's a message that their needs are not taken seriously by mainline community.

* I suspect game developers using boost are major source of swp as boost upgrades are often API incompatible so sticking to old version is tempting...