On Fri, May 27, 2011 at 11:20 PM, Alexander Sack asac@linaro.org wrote:
Hi Jim,
On Fri, May 27, 2011 at 1:06 PM, Jim Huang jim.huang@linaro.org wrote:
Hello list,
If you build Android using gcc-linaro-4.5-2011.05 [1], you will encounter a problem that bootanimation shows endless. It results from the mis-optimization in libgui, which handles the operations in Android SensorManager.
To work around this problem, you can apply the following patch:
--- a/libs/gui/Android.mk +++ b/libs/gui/Android.mk @@ -18,6 +18,8 @@ LOCAL_SHARED_LIBRARIES := \
LOCAL_MODULE:= libgui
+LOCAL_CFLAGS += -O0
in channel you said that -O1 is also working ... do we need O0 here?
one idea would be to make a list of all optimizations that come for O2 and then spin builds with adding one at a time ... in that way we can narrow down things. Not sure if that would be helpful for fixing the issue.
we definitly should file a bug against linaro-android project and then also add gcc-linaro project so it gets visibility of toolchain WG.
Hi guys. Yip, let's start doing this properly. Can I suggest the same as the Ubuntu relationship and methods? Basically:
* You find an issue * Log a bug on Launchpad against the component or, failing that, linaro-android * Figure out if it is a toolchain or package problem * Figure out if there is a work around such as changing the optimisation level
If it is a toolchain issue: * Feel free to do a work around in the package * Add the right tags so you can revert the workaround in the future * Mark the bug as affecting gcc-linaro * Provide sufficient information to reproduce the bug - preprocessed source would be great!
and we'll get on to it.
We'll need some help in setting up a test environment. Note that a lot of the triage work is on the distribution side (i.e. Android).
-- Michael