=== 64 bit atomics * I got the race in membase down to a futex issue, and asking dmart pointed me at a kernel bug that affects recent kernels where a fix had gone in about a month ago. That was a nasty one! * I've still got a few bugs left; most are turning out to be timing races in the test code (e.g. one that times out after 2seconds but the code takes around 1.7 seconds ish - but if something else gets in trips over the line, and another one where it did a recv_from on a socket but only got the start of a message, presumably because the sender had used multiple sends). It's tricky going because the tests are a combination of most scripting languages (perl, python, ruby with a splash of Erlang). I've so far found no bugs in the atomic code. * I looked at apr and SDL-1.3; both of which use atomics; but end up not using 64bit atomics; the tendency is for them to ensure they can do atomics on long and on a void*; both of which for us are 32bit.
=== String routines * I've got the Newlib A15 optimised memcpy running in a test harness at the moment for comparison. === Listening to connect * I listened in to a few connect sessions each day; the 1st day or so was 3/4 lost on audio systems that didn't work (I'm especially annoyed at not being able to hear the QEMU for A15/KVM session and toolchain support for kernel). The Rypple session was rather lost through the lack of any screen share or slides. _______________________________________________ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
