On 4/04/2012, at 6:28 AM, Fu, Chao-Ying wrote: > Andrew Pinski wrote: >> The point is mips*-*-* is big endian and mipsel*-*-* is little endian. >> And doing adding a target which says mips-linux-android which is >> little-endian is just backwards. Is there anyway to fix the target >> triplet to be mipsel-linux-android including inside the official NDK? >> If not then we have a broken triplet for android. > > I agree with what you said. > > The simplest fix is that mips-linux-android still generates big-endian code > as the MIPS target triplet design. Don't ever set it to generate > little-endian code automatically. > For MIPS GCC Android patches to merge to FSF GCC trunk, we will never change > endiannes. > > Note that we did use a regular mips-linux-gnu GCC to compile Android systems > by using -EL. > The target of "mips-linux-android" is just invented to work with NDK scripts. > And people can freely create "mipsel-linux-*" toolchains to compile Android > systems directly, > or create "mips-linux-*" toolchains to compile Android systems with -EL. > > The MIPS NDK script patch was just merged to googlesource last night. > I can work on another patch to use -EL options, but to let > "mips-linux-andoird" generate big-endian code. Is this solution ok for you?
I encourage you to submit the MIPS Android patches to gcc-patches@. And, as long as your changes preserve the status quo of mips-*-* being big-endian by default and mipsel-*-* being little-endian by default, there should be no major obstacles to merge those in. Thank you, -- Maxim Kuvyrkov CodeSourcery / Mentor Graphics
