bugs on armel) upstream.
* binutils: Committed a fix for ARM EABI tests upstream.
* Lots of admin stuff.
== Plan ==
* Get binutils testsuite green in a native configuration (fix LP #812276).
* Investigate getting binutils testuite automated via cbuild/Lava.
* More bugs...
--
Will Newton
there
was a Connect session about that?).
Thanks,
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
check in cbuild/LAVA.
* Get newlib memcpy patch committed.
* Investigate testing memcpy on big endian (qemu user, models?).
* IFUNC...
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http
== Progress ==
* Short week (2 days)
* Tested memcpy on big endian.
* Updated newlib memcpy patch.
* More digging into glibc IFUNC.
== Issues ==
* None.
== Plan ==
* Try and get newlib mempcy patch accepted.
* IFUNC...
--
Will Newton
Toolchain Working Group, Linaro
wish to
formally support gold and fix the broken make check.
Does anybody have any objections to doing that?
Thanks,
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http
.
* Submit memcpy IFUNC patch to glibc list.
* Get binutils tests into cbuild.
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
.
== Plan ==
* Submit a patch for binutils testsuite failure on precise.
* Complete work on glibc memcpy iFUNC patch.
* Follow up binutils IFUNC patch.
* AArch64 IFUNC next...
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
blocked on upstream review, 1 blocked on Android team.
== Plan ==
* Should get binutils IFUNC patch committed Monday.
* Need to ping other patches again.
* More work on AArch64 IFUNC.
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain
-strings.
* AArch64 IFUNC code and tests beginning to take shape.
== Issues ==
* None.
== Plan ==
* Another respin of glibc memcpy patch (last one?).
* More work on AArch64 IFUNC.
* May get time to look into gdb bug Peter found.
* 4 day week due to bank holiday.
--
Will Newton
Toolchain Working
be doing much building at the moment.
== Plan ==
* Complete AArch64 IFUNC support and submit a patch.
* Look further at gdb bug if I get time.
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain
might be worth looking into prefetching the data, either manually or
maybe try -fprefetch-loop-arrays?
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
memcpy.
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
memcpy problem on Galaxy Nexus.
== Issues ==
* binutils make ; make check takes over 24 hours on foundation model!
== Plan ==
* Respin AArch64 IFUNC binutils patch once relocation number allocated.
* Setup git mirrors for binutils, glibc and newlib.
* Android memcpy issue.
--
Will Newton
aarch64-elf testsuite issues with AArch64 ifunc patch.
* Investigated glibc malloc and alternatives.
== Issues ==
* None.
== Plan ==
* Submit new AArch64 ifunc patch after testing complete.
* Finish getting git mirrors setup.
* Look at some gdb testsuite failures.
--
Will Newton
Toolchain
ther gdb testsuite fixes.
* Some research into malloc.
== Issues ==
* None.
== Plan ==
* Create release branches for libraries & tools and improve docs.
* More gdb fixes.
* More malloc reading.
--
Will Newton
Toolchain Working Group, Linaro
__
`
* Questions? [ask Linaro](http://ask.linaro.org/).
* Interested in commercial support? inquire at [Linaro
support](mailto:supp...@linaro.org)
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain
Linaro](http://ask.linaro.org/).
* Interested in commercial support? inquire at [Linaro
support](mailto:supp...@linaro.org)
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http
`
* Questions? [ask Linaro](http://ask.linaro.org/).
* Interested in commercial support? inquire at [Linaro
support](mailto:supp...@linaro.org)
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain
==
* None.
== Plan ==
* Fix AArch64 ifunc issue.
* Fix gdb.thread issue.
* strlen
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
On Thu, Jun 20, 2013 at 2:41 PM, Thomas Petazzoni
wrote:
> Hello,
>
> I'm facing a bizarre problem with an armeb toolchain built by
> Buildroot. I'm also posting this to the crossgcc@ list since there are
> some gcc/binutils experts out there.
>
> First, a little bit of background. ARM Big Endian
benchmarks.
* gerrit review of memcpy change ongoing.
== Issues ==
* None.
== Plan ==
* Reproduce AArch64 ifunc issue.
* Resolve gerrit memcpy review if possible.
* Start work on malloc test and benchmark framework.
--
Will Newton
Toolchain Working Group, Linaro
cortex-strings and newlib for review.
== Issues ==
* None.
== Plan ==
* Prepare for Connect.
* Resubmit memcpy to gerrit as requested.
* Respin AArch64 ifunc patches against latest head.
--
Will Newton
Toolchain Working Group, Linaro
___
linaro
when the bot
> passes 90%, it shuts itself off.
It may also be worth examining your power supplies and see if they are
providing enough current to run the chip this hot reliably. A bench
supply could eliminate this possibility conclusively.
--
Will Newton
Too
.
* Preparation for Connect.
== Issues ==
* None.
== Plan ==
* Connect all week
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro
testsuite patch (my gdb patch queue now empty)
* Committed two of Omair's gdb patches
== Issues ==
* None.
== Plan ==
* Produce some malloc benchmark graphs
* Progress the stack guard work
* Start writing some malloc code
--
Will Newton
Toolchain Working Group, L
://lists.linaro.org/mailman/listinfo/linaro-toolchain)
* Linaro Toolchain IRC channel on irc.freenode.net at `#linaro-tcwg`
* Questions? [ask Linaro](http://ask.linaro.org/).
* Interested in commercial support? inquire at [Linaro
support](mailto:supp...@linaro.org)
--
Will Newton
Toolchain
, reading etc.
* Started work on malloc code.
* Booked flights for LCU13!
== Issues ==
* None.
== Plan ==
* Deal with any test feedback on IFUNC patches.
* malloc
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro
== Progress ==
* 4 day week (Friday off)
* Improve malloc benchmarking further.
* Writing and reading malloc code
== Issues ==
* None.
== Plan ==
* Possible eglibc 2.18 release
* Possible gdb release
* More malloc
--
Will Newton
Toolchain Working Group, Linaro
malloc implementation functionally complete
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
functionally complete
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
==
* Further malloc work
* Get glibc patches applied upstream
* Complete wiki cleanup
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro
rchitectural details (although you
could in theory extract this information in the resolver if it is
easily accessible in userspace).
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
1130a2dde6359e3709b7e318e9d88a
It's not an upstream commit but fixes up the merge in a pragmatic manner. ;-)
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
from
> my area of expertise :-)
Not using the HWCAP bits. It may be possible to pull the information
out of a register somewhere, but AFAIK it's privilege protected so not
possible from userspace.
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
* Committed strlen code to glibc
== Issues ==
* None
== Plan ==
* Get glibc patches applied upstream
* More malloc
* Look into stack guard and pointer guard stuff for ARM
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
://ask.linaro.org/).
* Interested in commercial support? inquire at [Linaro
support](mailto:supp...@linaro.org)
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman
possible
* Get back to malloc and stack guard work
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
== Plan ==
* Visit Linaro in Cambridge from Tuesday to Thursday (see you there!)
* Submit glibc malloc benchmark
* Get benchmark numbers for tweaked memcpy
* Start glibc pointer guard work
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain
glibc ARM pointer guard work
== Issues ==
* None
== Plan ==
* gdb 2013.09 release
* Various small items arising out of meetings last week
* Complete glibc ARM pointer guard
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing
://ask.linaro.org/).
* Interested in commercial support? inquire at [Linaro
support](mailto:supp...@linaro.org)
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org
little bit of time on malloc
* Built office furniture!
== Issues ==
* None
== Plan ==
* Finish off pointer guard
* Hopefully back to malloc
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain
AArch64 GOT layout patches.
== Issues ==
* None
== Plan ==
* Backports for 2013.10
* Follow up qemu patch
* malloc
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http
t; Error: unknown cpu `cortex-a53'
> Error: unrecognized option -mcpu=cortex-a53
I believe this is an assembler error, as the assembler only supports
these CPU types on binutils trunk. Have you tried passing
-mtune=cortex-a53 instead?
--
Will Newton
To
malloc
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
://lists.linaro.org/mailman/listinfo/linaro-toolchain)
* Linaro Toolchain IRC channel on irc.freenode.net at `#linaro-tcwg`
* Questions? [ask Linaro](http://ask.linaro.org/).
* Interested in commercial support? inquire at [Linaro
support](mailto:supp...@linaro.org)
--
Will Newton
Toolchain Working Group
`
* Questions? [ask Linaro](http://ask.linaro.org/).
* Interested in commercial support? inquire at [Linaro
support](mailto:supp...@linaro.org)
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain
== Progress ==
* Relased gdb 7.6.1 2013.10
* Respin of qemu VSEL patches
* Bug fixing and performance measurement on malloc
== Issues ==
* None
== Plan ==
* Refactor malloc to improve performance
* Prepare for Connect
--
Will Newton
Toolchain Working Group, Linaro
== Progress ==
* Ongoing refactoring of malloc to improve performance
* Preparation for Connect
== Issues ==
* None
== Plan ==
* Linaro Connect US
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain
-tcwg`
* Questions? [ask Linaro](http://ask.linaro.org/).
* Interested in commercial support? inquire at [Linaro
support](mailto:supp...@linaro.org)
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain
glibc memory manual and aligned_alloc patches
* malloc
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
e gdb hardware breakpoint issue
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Wednesday afternoon
== Plan ==
* Respin and submit glibc docs patches
* Submit glibc aarch64 ifunc code
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman
==
* None
== Plan ==
* aarch64 qemu
* UK Memory Management Network Workshop on Friday
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro
== Progress ==
* Rework QEMU AArch32 ARMv8 patches (3/10, TCWG-47, TCWG-48)
* Further work on QEMU AArch64 FP patches (5/10, VIRT-183)
* UK Memory Management Network Workshop on Friday (2/10)
== Issues ==
* None
== Plan ==
* More QEMU AArch64 FP
--
Will Newton
Toolchain Working Group
55807568
> x290x7fe4d0 549755806928
> x300x4b4ed4 4935380
> sp 0x7fe4d0 0x7fe4d0
> pc 0x4b4b90 0x4b4b90
> std::char_traits, std::allocator > > >::get() const+36>
> cpsr 0x2000 5
On 12 December 2013 21:02, Michael Hudson-Doyle
wrote:
> Hi,
>
> Thanks for the respsonse.
>
> Will Newton writes:
>
>> On 12 December 2013 08:00, Michael Hudson-Doyle
>> wrote:
>>> Hi all,
>>>
>>> I have a bit of a strange one. I
On 12 December 2013 21:59, Michael Hudson-Doyle
wrote:
> Will Newton writes:
>
>> On 12 December 2013 21:02, Michael Hudson-Doyle
>> wrote:
>>> Hi,
>>>
>>> Thanks for the respsonse.
>>>
>>> Will Newton writes:
>>>
>&g
On 12 December 2013 23:14, Michael Hudson-Doyle
wrote:
> Will Newton writes:
>
>> On 12 December 2013 21:59, Michael Hudson-Doyle
>> wrote:
>>> Will Newton writes:
>
> [snp]
>
>>>> I would guess that 0x64c000 is the base of the GOT and 776
day week next week then off until Jan 8th
* Wrap up qemu work to a good state to handover
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro
aarch64 ld backend) but was intended to be fixed by the rework of
the same code in 1419bbe5712af8a43f1d63feb32687649563426d. However I
was never actually able to reproduce the failure case (I saw binaries
that were broken so I know it could happen) so the fix was somewhat
speculative. Hence I am
On 17 December 2013 07:53, Michael Hudson-Doyle
wrote:
> Michael Hudson-Doyle writes:
>
>> Michael Hudson-Doyle writes:
>>
>>> Will Newton writes:
>>>
>>>> On 16 December 2013 03:36, Michael Hudson-Doyle
>>>> wrote:
>>>
!
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
lation unit where the reference is).
Usually the cause is either an assembly coding error or some code
being built without -fPIC.
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
the
> comparison failing inside of Qt shared libraries is breaking code on ARM, as
> -Bsymbolic is set by default there.)
Thanks for the report and testcase.
The attached patch to ld may help. I am not yet sure whether or not it
is the correct approach but if it works for you that would be
int
* Hopefully push glibc ARM pointer encryption fix for 2.19
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
l probably need to attached patch as well since some of the
>> linaro patches break namespace support :(
I believe the kernel build system can get you the pre-processed source
with, e.g.:
# make lib/raid6/neon4.i
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
On 16 January 2014 10:04, Giuseppe D'Angelo wrote:
> Hello Will,
>
> Il 10/01/2014 15:50, Will Newton ha scritto:
>>
>> Thanks for the report and testcase.
>>
>>
>> The attached patch to ld may help. I am not yet sure whether or not it
>> is the c
mplete outstanding QEMU work
* ARM setjmp/longjmp SystemTap probes
* malloc
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
WG-378)
* Ported Python cffi package to AArch64, submitted upstream (1/10)
* Fixed bug building glibc for armv4 (1/10)
== Issues ==
* Broadband down for 3 hours on Wednesday afternoon
== Plan ==
* Follow up QEMU patches and maybe post v2
* malloc
--
Will Newton
Toolchain Working Group,
setjmp/longjmp changes
* malloc benchmarking and improvements
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
l has lots of these errors, but disables the warning explicitly:
# disable pointer signed / unsigned warnings in gcc 4.0
KBUILD_CFLAGS += $(call cc-disable-warning, pointer-sign)
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
benchmark graphing script
* newlib release
* gdb 7.7 release (build an rc to troubleshoot releasing from git)
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org
==
* QEMU CRC instructions
* Finalize slides for Connect
* malloc
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
work
* Preparation for Connect
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
== Progress ==
* 3 day week (off Monday and travelling Friday)
* QEMU ARMv8 CRC instructions (2/10, TCWG-52)
* Slides for Connect (3/10)
* Investigating AArch64 setcontext issue (1/10, TCWG-410)
== Issues ==
* None
== Plan ==
* LCA14
--
Will Newton
Toolchain Working Group, Linaro
opriate value, set arm mode and function type
of sTestArnDale symbol)
--
Will Newton
Toolchain Working Group, Linaro
test_arndale.s
Description: Binary data
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
; __pthread_key_create + 0
>
> ...
>
> ^^...note the __pthread_key_create relocation I am interested in...
>
> I would expect the RELASZ in the dynamic section to be 0x2058 instead of 0.
>
> Any tips to what could be wrong?
I can't see any obvious way this could hap
IG_CC_OPTIMIZE_FOR_SIZE
>
> KBUILD_CFLAGS += -Os $(call cc-disable-warning,maybe-uninitialized,)
>
> else
>
> KBUILD_CFLAGS += -O0
It is not possible to build the kernel with -O0 due to various
requirements for inlining and register allocation. You could try -O1
or -Og (if your compi
== Plan ==
* Resolve eglibc mirror situation
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
graphing script
* Holiday on Friday
== Issues ==
* Couple of hours power outage on Monday
== Plan ==
* Get outstanding glibc and binutils patches committed
* Reorganise JIRA cards for malloc work
* glibc benchmarking
--
Will Newton
Toolchain Working Group, Linaro
)
* Investigate a couple of issues raised by member services and on lists (2/10)
== Issues ==
* None
== Plan ==
* Resurrect glibc malloc benchtest
* More glibc benchmark infrastructure work
* Check status of glibc ARM port build warnings
--
Will Newton
Toolchain Working Group, Linaro
microbenchmark (2/10, TCWG-160)
* Various small binutils and glibc patches (1/10)
== Issues ==
* None
== Plan ==
* Submit patch for glibc malloc microbenchmark
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro
t. For example
if you run arm-linux-gnueabihf-readelf --debug-dump on the object and
look for DW_AT_comp_dir it should show you where objdump will look for
source files by default. You can manipulate this path with the
--prefix and --prefix-strip options if your source code is in a
different path.
--
)
== Issues ==
* None
== Plan ==
* More glibc and malloc microbenchmark work
* malloc macro benchmark planning
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org
, etc. (1/10)
== Issues ==
* None
== Plan ==
* malloc benchmarking/implementation work
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro
-benchmarks for malloc (1/10, TCWG-441)
* Investigate glibc single-thread optimization (1/10, TCWG-436)
== Issues ==
* None
== Plan ==
* Further work on glibc single-thread optimization
* More malloc macro-benchmark stuff
--
Will Newton
Toolchain Working Group, Linaro
== Plan ==
* Various bits of patch followup
* More malloc macro-benchmark work
* See how single thread optimization discussion goes
* glibc benchmark graphing?
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro
==
* Develop a good general way to measure memory usage of complex applications
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
memory usage (4/10, TCWG-441)
* Trying to get NX working on Fedora 20 (1/10)
== Issues ==
* None
== Plan ==
* Get postgresql and hopefully others working with new benchmark setup
* Figure out how to make NX work
--
Will Newton
Toolchain Working Group, Linaro
failures on aarch64 (2/10)
* Meetings, admin (1/10)
== Issues ==
* None
== Plan ==
* More malloc application benchmarking
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http
binutils/linaro-2.24.0-2014.03 to
> binutils/linaro-2.24.0-2014.05.
>
> == Plans ==
>
> * Push pending patches.
>
> == Planed leaves ==
>
> * June. 2.
>
> ___
> linaro-toolchain mailing list
> linaro-toolchain@list
refactoring malloc microbenchmark
* Work on results plotting code for benchmarks
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
running for validation
* More malloc benchmarking
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
by Maxim (1/10)
* Patch review and followup (1/10)
* Meetings, admin (1/10)
== Issues ==
* None
== Plan ==
* Ubuntu on wg?
* Resubmit malloc microbenchmark
* Rework postgresql benchmark to use unix domain sockets
--
Will Newton
Toolchain Working Group, Linaro
Is that on cards for backport?
I'll backport it for 2014.07. It may be possible to work around this
by passing --disable-werror to the configure script.
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing li
Friday (2/10)
* Still no luck on getting Ubuntu on wg boards
== Issues ==
* None
== Plan ==
* Make sure we have everything we need for glibc freeze at month end
* malloc app benchmark work
--
Will Newton
Toolchain Working Group, Linaro
___
linaro
hain/binaries/gcc-linaro-armeb-linux-gnueabihf-4.8-2014.04_linux.tar.xz
The instruction is valid and encoded correctly as far as I can tell. I
would suspect that this exception may be related to the kernel VFP
handling code.
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
glibc, binutils and gdb (1/10)
* Investigated language runtimes (1/10)
* Meetings (1/10)
== Issues ==
* None
== Plan ==
* More glibc patch work for the freeze (1st July)
* malloc benchmarking
--
Will Newton
Toolchain Working Group, Linaro
___
linaro
bugzilla/JIRA/upstream
* malloc benchmarking
* glibc patches
--
Will Newton
Toolchain Working Group, Linaro
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
/10)
* Get binutils ARM testsuite all passing on EABI, mostly on OABI (2/10)
* glibc patch review and build warning fixes (2/10, CARD-341)
* Annual leave on Friday (2/10)
== Issues ==
* None
== Plan ==
* 4 days in Berlin
* Travel to Cauldron
--
Will Newton
Toolchain Working Group, Linaro
1 - 100 of 134 matches
Mail list logo