On Tue, Apr 3, 2012 at 10:45 AM, Fu, Chao-Ying <f...@mips.com> wrote: > Andrew Pinski wrote: > >> On Mon, Apr 2, 2012 at 1:55 PM, Fu, Chao-Ying <f...@mips.com> wrote: >> > It basically sets the MIPS target to little-endian MIPS32 >> for mips-linux-android. >> >> That seems broken because mips-*-* is big-endian and mipsel-*-* is >> little-endian. Is any way of fixing that before even trying to >> submitting the patch? Because it will be the only port for mips which >> is the opposite endian which makes it out of place. > > We fixed the MIPS target to little endian, because there is only one > MIPS ABI in official NDK for Android: little-endian MIPS32 release 1. > NDK scripts are tested with mips-linux-android. (We didn't test > mipsel-linux-android targets.) > Note that Android software components (ex: google v8, webkit jsc) may be > coded for > little-endian targets only. > > If GCC doesn't set the MIPS Android targets to little endian, it will be > easy to > add a small patch into googlesource in the future. Ex: Add -EL options for > compilation/linking. > Thanks!
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. Also it seems broken they are coded for little-endian only but that is a different point all together. Also there are a few MIPS64 processors out there which default normally to big-endian (octeon). Thanks, Andrew Pinski
