This got stalled ages ago, and in the meanwhile the Arm stuff has been
reverted, the last of those as late as
6e51ca5959d9e5159fdd75c0462c900d342f2cce. So we're back to square one and this
PR is no longer applicable, if/when there's something more to do lets start
afresh in a new ticket/PR.
Closed #946.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/946#event-4266226465___
Rpm-maint mailing list
cc: @berolinux
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/946#issuecomment-557843099___
Rpm-maint mailing list
Possibly a straight up revert is the right thing to do. I was trying to keep
the intention of the previous patch as much as possible.
In terms of VFP/VFPv3 it is a requirement of ARMv8, but in theory (although I'm
not sure why you'd want to) you could have softfp builds on armv8 so to keep
Fixing a fix of a fix is always a bit of a red flag.
The unification in commit 8c3a7b8fa92b49a811fe36b60857b12f5d7db8a8 assumes that
we'll want to keep adding these modifier letters like 'h' forever more for all
new versions to come, but isn't VFP/VFPv3 capability a requirement in >= armv8
Theres some issues with the detection of particular Arm hardware
features. We never want to use the crypto feature as part of rpm
functionality, its deployment is widely variable, and the HW
optimisation should be run time detected with fall back through
various optimisation paths.
The 8c3a7b8fa
