On 13 October 2011 05:03, Alexander Sack a...@linaro.org wrote:
On Thu, Oct 13, 2011 at 1:12 PM, Tony Mansson tony.mans...@linaro.org
wrote:
* Strict-aliasing violations in 2.3.5 have been fixed.
I remember that we disabled -Werror because of various issues ... with those
strict-aliasing
The toolchain builds featuring the 11.09 release from the toolchain WG
are ready:
https://android-build.linaro.org/builds/~linaro-android/toolchain-4.6-2011.09/
https://android-build.linaro.org/builds/~linaro-android/toolchain-4.5-2011.09/
Please update your builds to use it, and let me know if
On 9 September 2011 08:35, Christian Robottom Reis k...@linaro.org wrote:
Good job on proactively looking for bustage. I assume you guys worked
out a plan with Michael on how to provide feedback on the issues we
find -- let me know if that needs work.
I presume normal bug reports will do the
On 29 August 2011 07:11, Christian Robottom Reis k...@linaro.org wrote:
I don't think we should keep the bug open pending feedback from
upstream, but we definitely should start a thread to figure out why
upstream has chosen to use FBIOPUT_VSCREENINFO.
We know that -- they chose it because some
On 27 August 2011 21:45, Bernhard Rosenkranzer
bernhard.rosenkran...@linaro.org wrote:
That's exactly what Android does in a couple of places, e.g.
system/core/init/logo.c, function fb_update() [that one actually calls
FBIOPUT_VSCREENINFO _twice_ to update the screen]
hardware/libhardware
Hi,
OK, here's one preliminary theory after I dragged Jason to a conversation
from his weekend in a vacation.
Thanks! Could have waited until Monday of course, but it's great to
have another starting point to work on over the weekend.
There could be mis-use of the framebuffer's
On 21 August 2011 15:00, Michael Hope michael.h...@linaro.org wrote:
Sorry, silly question, but does Android use the glibc dynamic linker?
No, they really like reinventing the wheel. Bionic comes with its own
dynamic linker.
If not, does its linker support other hash styles?
It looks like it
Hi,
the 11.08 Android toolchain RC is ready:
https://android-build.linaro.org/builds/~linaro-android/toolchain-4.6-2011.08/#build=6
Hi,
On 18 August 2011 19:40, Chao Yang chao.y...@linaro.org wrote:
The results can be found
at https://wiki.linaro.org/ChaoYang/Sandbox/gccoptimization.
Interesting... I'd have expected getting rid of -fno-strict-aliasing
gives the biggest performance boost, but I'd have expected O3 to be a
).
The TOOLCHAIN_URL is
https://android-build.linaro.org/jenkins/job/linaro-android_toolchain-4.6-2011.08/5/artifact/build/out/android-toolchain-eabi-linaro-4.6-2011.08-5-2011-08-17_09-40-30-linux-x86.tar.bz2
ttyl
bero
On 17 August 2011 01:46, Bernhard Rosenkranzer
bernhard.rosenkran...@linaro.org
On 10 August 2011 12:44, Michael Hope michael.h...@linaro.org wrote:
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
on.
If it actually builds on 32 bit hosts, I agree -- but in that case we
should
Hi,
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
Hi,
I just spotted this bit in Android's Makefiles (inherited that way from AOSP):
TARGET_arm_CFLAGS := [...] -fstrict-aliasing [...]
[...]
TARGET_thumb_CFLAGS := [...] -fno-strict-aliasing [...]
This general assumption that arm code can handle strict aliasing, but
thumb code can't, seems odd.
On 28 July 2011 21:37, Angus Ainslie angus.ains...@linaro.org wrote:
I have a android manifest that builds fine on my local build server
with -j4 for concurrent makes.
Have you tried doing a re-download locally?
The issue I've had that resulted in the same error (while it may not
be elfcopy for
=== Highlights ===
* Multimedia test extensions (esp. ffmpeg builder)
* Built toolchains
* Got i.MX53 related files into the tree
=== Plans ===
* Check if i.MX53 build works; fix if it doesn't
* Sort out test content hosting for multimedia test
=== Issues ===
* Atrocious connectivity while
15 matches
Mail list logo
