Make arm-qemu builds ARMv4T compliant (was ARMv6) to support more devices #902
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By submitting this pull request, I confirm the following:
How familiar are you with the codebase?:
10
Explicitly specify the building host to achieve true ARM Debian compliance with the cross-compiled build. We remove concurrent building of the dependencies as this can lead to compiler segmentation faults on many-core machines with a lot of concurrency in the emulator.
Even though this build only requested ARMv5 compliance, the produce code actually generated a binary that is even ARMv4T complaint:
Even when this is not the expected outcome, any ARMv5TE processor will be able to run ARMv4T code. And as the compiler generated ARMv4T code while it was allowed to generate ARMv5TE means that, despite the fact that all compiler optimizations are enabled, no ARMv5TE-specific instructions are useful here and the generation of ARMv4T-compliant code is not slower by any means (due to missed optimizations).
The PR updating the FTL builds for ARMv4T-compliance will also address the changed architecture in the tests. This has to come after this PR was merged.