Why are our Android toolchains 32bit?
michael.hope at linaro.org
Wed Aug 10 19:44:59 UTC 2011
On Thu, Aug 11, 2011 at 2:29 AM, Bernhard Rosenkranzer
<bernhard.rosenkranzer at linaro.org> wrote:
> while working on some improvements, I noticed that our Android
> toolchain binaries are built as 32-bit x86.
> Is there any reason for this (other than "we inherited it from AOSP")?
> While it doesn't matter much, it doesn't make much sense to me -
> Android can't currently be built on 32-bit machines (so it's not about
> having one binary that will work for mostly everyone - but I suspect
> that's exactly where it started back in the times of Android 1.0), so
> why introduce dependencies on a 32-bit libc and slow things down
> If nobody complains, I'll remove the "-m32" flag from the Android
> toolchain builds - let's see how much we can speed up the build
> process itself without putting any real work into it...
I'd leave it as 32 bit. This gives you a single binary toolchain that
can run on 32 bit and 64 bit hosts, no matter what host it was built
More information about the linaro-dev