Hi Guys,
I have two questions:
(1) I have download gcc-4.9 tool chain from
http://releases.linaro.org/14.08/components/toolchain/binaries.
The kernel for the release
(http://releases.linaro.org/14.08/components/kernel/linux-linaro) is
3.16. So can we assume the kernel headers found in the tool chain
installation from the link above belongs to linux version 3.16?
(2) Also, I ubuntu wiki indicates that starting with Ubuntu 12.04 they
are using linaro gcc packages for arm64
(https://wiki.ubuntu.com/ToolChain). Is there an easy way to find what
linaro-release (for tool chain) will be compatible with Ubuntu 14.10
aarch64 image?
Thanks,
Aravind
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
Short week (off Thu/Fri - 4/10)
== Progress ==
* GCC trunk (1/10)
- investigated bare-metal broken builds for aarch64 and arm
(--with-mode=thumb)
Setting LDFLAGS_FOR_TARGETS=-specs=rdimon.specs fixes the
libstdc++ build problem for aarch64. Not sure if that's expected.
* Neon intrinsics tests (2/10)
- submitted a new set of tests for review
* 4.8-2015.04
- branch merge committed after validation
* Validation (1/10)
- looking at tests instabilities
* Misc (2/10)
- meetings, conf-calls, emails, ....
== Next ==
* Neon intrinsics tests
* GCC trunk/bare metal
* Validation
== Progress ==
LLDB development
-- Finished most of work for ARM watchpoints and hardware breakpoints
[3/10] [TCWG-770]
-- Added hardware breakpoint handlers for AArch64 [1/10] [TCWG-771]
-- Debugging for ARM watchpoints not hitting the hardware watchpoint
Set/Clear handlers. [3/10] [TCWG-770]
-- Setting up development environment on Google Nexus 7 Android device. [1/10]
Miscellaneous [2/10]
-- Meetings, emails, discussions etc.
-- Submission of French visa application
== Plan ==
LLDB development
-- Submit ARM and AArch64 hardware breakpoint and watchpoints code for review
-- Fix issues with hardware watchpoints and try to run tests on Nexus 7
-- Figure out debugging using gdb on Nexus 7
Miscellaneous
-- Travel to Islamabad for visa interview, out of office on
wednesday 13th May 2015.
-- Half day out of office on Monday 11th and Tuesday 12th May due to
power outage in the area.
Short week: Friday off
== Progres ==
* Linaro-GCC 4.8-2015.04
- have to redo the fsf-4.8 branch merge
- results stability issue, probably caused by a race condition in
the testsuite similar to one already fixed by Maxim
* Validation
- a few updates to our jobs on ci.linaro.org
* Neon intrinsics tests
- resumed port of existing testsuite to GCC
* Misc
- meetings, conf-calls, emails, ....
== Next ==
Short week (Thu/Fri off)
* Linaro-GCC-4.8-2015.04
* Neon intrinsics tests
Friday off (WWII Memorial Day)
== Issue ==
* none
== Progress ==
o Upstream GCC (4/8)
* [TCWG-762] - GCC Maintenance
- PR64208 (iWMMXT LRA bug):
Committed in trunk.
- PR65924 (ICE on arm-none-eabi):
Fixed and committed at rev. 22572
* Flags for Cortex-a53 erratum #84341 workaround:
- Committed in trunk
- To be backported into FSF 5.1 and 4.9 branches
o 2015.04 re-spin (2/8)
* Snapshot tarball deployed
o Misc (2/8)
* Various meetings
* Reviewed and validated a libunwind ARM patch
* Played a bit with docker AArch64 image (based on UMEQ)
https://registry.hub.docker.com/u/mickaelguene/arm64-debian/
== Plan ==
- Short week (off Thu, and Fri)
- Continue upstream pending work
(Public) Holiday [2/10]
Benchmark automation - TCWG-360 [6/10]
* More unit tests
* Refactoring - test writing is an effective spotlight
* Experimented with LAVA log streaming as a 'listener' replacement
** Reduces complexity, for (possibly insignificant) costs in
generality and scalability
* Gave some thought to results storage, benchmarking of restricted targets
Misc [2/10]
=Plan=
Pick a direction on streaming vs listeners, write down the reasoning
Follow up (close out?) results storages and restricted targets
Write more tests, refactoring where appropriate
Holiday [2/10]
Benchmark automation - TCWG-360 [5/10]
* Finished rolling backbench patches into review
* Submitted some test suite patches to reduce the number of untested cases
* Began writing tests for benchmarking in general
Misc [3/10]
== Progress ==
* Upstream GCC (4/10)
- TCWG-779 Vector rtx costs for AArch64 ACKed to commit.
- Asked to do fresh regression and benchmarking
- re-based to latest trunk
- Trunk is broken and narrowed down the failure to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66066
- Fixed and regression testing finished. Setting up benchmarking for
spec2k before committing.
* IRA (5/10)
- Looked at https://bugs.linaro.org/show_bug.cgi?id=540 (TCWG-773
Median of three has unneeded register moves)
- https://bugs.linaro.org/show_bug.cgi?id=1532
* Misc (1/10)
- gcc-patches, gcc-bugs list
- Meetings
== Plan ==
- Continue with gcc stage1 activities
- Look at register allocation
