On 08/11/2010 18:45, Loïc Minier wrote: > I would be careful when removing the march=armv4t and other flags; I > think it's the right thing to do, but other places might have to be > patched; for instance, I see ANDROID_FLAGS for instance has it > hardcoded, while it doesn't apply to linux/kfreebsd builds, there might > be some hidden nasty flags somewhere which motivated the addition of > this patch. I would grep the build log on armel for suspicious flags > like -march/-mcpu/-mtune and probably -marm/-mthumb*.
Well i'm now testing armel builds on qemu/squeeze, and discovered what follows. > -mno-thumb-interwork is a bit suspicious; I'm not entirely comfortable > on the architecture revisions and cases where these flags are > explicitly needed, but in any case the toolchain defaults should be > fine. It seems the only reason left for that flag is because v8 code complains about missing 'blx' instruction when arch is armv4t (the gcc default on debian). Reported at http://code.google.com/p/v8/issues/detail?id=590 > -fno-tree-sink seems to be a workaround for a compiler bug (disabling > an optimization). It was, gcc 4.4.5 has fixed the bug. > -Wno-psabi is undocumented in my version of gcc. See http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42748 not fixed in gcc 4.4.5-4. Regards, Jérémy. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
