== Progress ==
Was on vacation most of the week Mon - Wed leave (Thursday half day).
* Libssp support for AArch64 TCWG 23
Restarted the work. Looked at how X86 GCC generated code. Looking at
per thread support for libssp and compiler support.
== Plan ==
* Continue Libssp support for AArch64 TCWG-23
* Look at builtin return address behaviour in the absence of frame pointer.
==issues==
* LTO/PGO work stopped now since libssp support priority is more.
== Issues ==
* None.
== Progress ==
* Attended linaro Connect (Wk 28)
* OE Launchpad bug #1200620 :
[ICE while building Exynos5 kernel with current 4.8 branch]
- Issue due to a bad usage of unaligned load/store in HI mode
- Fix approved and committed upstream
- Release respin ongoing.
* Launchpad bug #1186218 :
[kernel doesn't boot on Arndale/Nexus with Linaro GCC 4.8]
- Discussed the issue at Connect
- Waiting for a reduce testcase from the kernel team.
* LRA on AArch64:
- Some regressions in the testsuite
- Debugging ongoing.
* LRA on AArch32:
- Still some issues with libgcc build in Thumb
- Back on this issue.
* 2013-08 4.8 release:
- Backports from trunk ongoing.
== Plan ==
* 4.8 Backports
* Summer break
== Progress ==
* Debugged gdb.mi and linux-nat code to investigate issues on arm.
* Cleared pending gdb patches.
* Listened to Connect sessions and key notes on youtube
* Follow up on travel hick ups and UK/US visa application
== Plan ==
* Review GDB current status and fill up JIRA with proposed future work
* Windup work on gdb test suite updates and submit remaining patches.
* Follow up on gdb patches
* Clear/Update JIRA cards
* File UK visa for meetings in September.
== Progress ==
* Attended Connect, did presentation and other stuff.
* Left Connect early to attend the Gnu Tool Cauldron. Ran BOF on
testing the toolchain, attended many talks including the one on
Graphite.
* Worked on modularizing cbuildv2 package parsing into functions so
bzr,svn,git URLs and tarball snapshots from toolchain64 work the
same.
* Added LLVM support to cbuildv2, Clang and the testsuites only work
if built separately for now.
* Reproduced build problem Viswanath was having with crosstool,
Zhenqiang knew the missing package(s) that kept C++ builds from
working.
* Built fsf 4.7 and 4.8 as well as Linaro GCC releases for July on Panda
board.
* Got spec200 benchmarks working on panda, ran them for the above
branches and releases.
== Plans ==
* Help Charlie come up to speed on building GCC.
* Run more benchmarks on the above branches and do graphs on
performance.
* See why for me on a panda, all the tests fail with make check.
* Find time to work on cbuild2 so Charlie can beta test it sometime
soon.
- rob -
== Issues ==
* None
== Progress ==
* Enable multi-arch for Linaro aarch64-linux-gnu build.
- Configure gcc with --enable-multiarch.
- Backport eglibc patches for rtlddir.
- Configure eglibc to set libdir, slibdir and rtlddir.
* Follow up the patch for pr57637.
* Reassociate X == CST1 || X == CST2 if popcount (CST2 - CST1) == 1
into ((X - CST1) & ~(CST2 - CST1)) == 0.
- Test is ongoing.
* Rebase conditional compare changes to trunk.
== Leave ==
* July 17.
== Plan ==
* Send out the conditional compare changes for Linaro internal review.
== Progress ==
Short week (3 days)
* Divmod
- Finished most of the work, patch upstream (r186390)
- Trying to lower remainder as divmod without sacrificing the div+mod
merge during legalization
* Buildbots
- One panda fails even at 920MHz, replaced with a new one
- Using decent power supplies now, should work a whole week
- Lab config is messed up, need to start from scratch
- Failed at 920MHz with decent power supply
- Giving up on Pandas as buildbots...
* Background
- Not many code reviews last two weeks, as Connect and the Pandas took
most of my spare time
- Test-suite's Lencod bug fixed upstream, no more need of dirty hacks on
stack offset calculation
== Plan ==
* Continue on divmod lowering, finding a way to merge Custom with Expand
lowering, so not to break the div+rem merge during legalization, but still
lower divmod as Custom. 64-bit types still use them.
* Study cross-compilation issues in Clang and LLVM, prepare a document on
how it works (or not), and what paths we can take to make it better in the
short/medium term.
* Follow up on Phoronix results and CBuild2 benchmarks, time allowing
== Progress ==
* Investigating glibc stack guard support
* Developed initial patches
* Raised ABI issue
* More malloc work
* Integrated tcmalloc into benchmark framework
* Improved benchmark repeatability
* Added Python benchmark script and graphing script
* Respin and commit gdb TLS 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, Linaro
Progress:
* attended Linaro Connect (wk 28)
* sent pull requests for target-arm/arm-devs queues
* resent virtio-mmio patchset; this is now ready for commit
and I will send a pullreq with it in next week
* finished off a cleanup of linux-user to remove the support
for configuring targets without threading support
* resorted todo list against cards
* started on getting v7 mach-virt into shape for upstreaming
-- PMM
Hi All,
I am new to linaro. so would like to know more about linaro.
Is linero alternative to yocto project.
does the tool chain support armv5te based SOC.
Ratheendran
Hi Folks,
I'm running two buildbots here at home and am getting consistent failures
from the Pandas because of overheating. I've set up a monitor that will
tell me the current CPU temperature and the allowed maximum, and when the
bot passes 90%, it shuts itself off.
The problem is that I'm running with heat-sinks and the boards are on top
of three fans, so there really isn't much more I can do to solve this
problem.
I personally think this is a hardware problem, since everything is in the
same die, CPU, GPU and RAM, and the physical dimensions of the chip are
quite small. I remember when Intel started overheating (around 486DX66) and
the die was huge (more head dissipation), plus RAM and GPU were separate,
and it still needed a hefty heat-sink.
It's true that gates are far smaller today, but it's not true that a dual
core 1.3GHz + GPU + RAM will produce less heat on a small die than a 66KHz
CPU on a huge die, so why anyone think it's a good idea to release a 1+GHz
chip without *any* form of heat dissipation is beyond my comprehension.
Manufacturers only got away with it, so far, because people rarely use 100%
of the CPU power for extended periods of time, because ARM devices end up
as set-top boxes, mobile phones and tablets. However, even those devices
will heat up when playing 2 h films or games, and they do have some form of
heat sink.
We, at the toolchain group, make things worse by using 100% CPU, 24 / 7,
something that Panda boards, or Arndales were not designed to do. However,
with ARM moving into the server space, their designs will have to be
re-thought, and what a better place than Linaro for making sure we get it
right?
For the time being, I believe we *must* have air conditioning in the Lab
all the time, and we *must* have heat-sinks on every board, and we *must*
monitor the CPU temperature of the boards, at least until we're comfortable
that they're not failing all the time.
Can we make a temperature monitor (like the one attached) a default feature
on Linaro Ubuntu distributions? We could dump that info to the syslog/dmesg
whenever it crosses the (say) 75% threshold, and report more often when it
crosses the 95%, possibly dumping the processe(s) that are consuming more
CPU at the time, to enable post-mortem debugging.
cheers,
--renato
As a side note, the quad-A9 ODroid does ship with a massive heat-sink,
which also serves as a fancy case. Quite clever, really.
