On Thu, 18 Apr 2013, Niels Möller wrote:
Martin Storsjö martin@martin.st writes:
On Wed, 17 Apr 2013, Niels Möller wrote:
I'm not going to do anything sophisticated about this before the 2.7 release (which I'd like to get out within a few days, at most two weeks). I could add an --enable-neon/--disable-neon flag, with default based either on /proc/cpuinfo (and some fix default for cross compilation), or on what the assembler accepts, as you suggest. Would that make sense?
That's certainly a good start.
Something along those lines checked in now. Testing appreciated.
For native compilation, configure checks /proc/cpuinfo, and for cross compilation, it checks what the assembler accepts.
This seems to be work as intended (after some very brief testing), thanks!
// Martin