o 4 days week.
o LLVM
* Machine outliner:
- Reduced CTMark issue, still working on it.
o Misc
* Various meetings and discussions.
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linar
== Progress ==
o GNU releases
* Various support on process and infra.
o LLVM
* Benchmarking job on-going
* Buildbots baby-sitting
* Completed EuroLLVM feedback
* Created ticket: outliner support on ARM
After internal and upstream discussions.
o Misc
* Various meetings and discussi
o 1 day off (2/10)
== Progress ==
o Extended validation (2/10)
* Extended validation now operational,
reporting enhancements investigations.
* Looked at gdb/guality unstable results.
* Reviewed some jobs.
o Linaro GCC (2/10)
* Scripted new Linaro development branch process.
o Up
On 27 April 2015 at 03:17, Prathamesh Kulkarni
wrote:
> == This Week ==
> * TCWG-619:
>
> * abe sysroot/libc issue
> While building chromium with development build of toolchain on
> arm-linux-gnueabihf, I get the following error:
> undefined reference to clock_gettime()
> Builds fine with release
== Issue ==
* none
== Progress ==
o Upstream GCC (8/10)
* [TCWG-785] ARM backend insn cleanup
- Validate and re-worked the patch
- About to be submitted upstream
* [TCWG-762] - GCC Maintenance
- PR64208 (iWMMXT LRA bug):
Found hardware to validate the fix (Thanks Riku
== This Week ==
* TCWG-619:
* abe sysroot/libc issue
While building chromium with development build of toolchain on
arm-linux-gnueabihf, I get the following error:
undefined reference to clock_gettime()
Builds fine with release toolchain build.
Symlinking libc in toolchain install directory to
sys
== Progress==
TCWG-435 needless busy-wait in lowlevellock.c (3/10)
* Patches ready, testing a bit slow & fiddly
TCWG-156 cortex-strings memset (3/10)
* Worried about noisy benchmarks
* Learned to use Lava
* Found some helpful internal docs
* Managed to tweak the code slightly
== Misc ==
Meetin
Short week, Easter Monday + child care (3/10)
== Issues ==
* Toolchain64 disk still full every 2 days
== Progress ==
* Linaro GCC 4.9 2014.04 release (3/10)
- Branch merge with FSF 4.9.1
- Release tarball available on releases.linaro.org
- Announcement will follow
* Launchpad bugs: (2/10)
== Issue ==
* None
== Progress ==
* More tests on shrink-wrap changes (TCWG-133, 6/10).
- Cortex-m3 tests exposes a data flow issue: New BB created after
dfinit does not have correct df_lr info.
- Collect Spec2k benchmarks on X86-64 and ARM.
* Linaro 4.9 binaries release (2/10).
- Update L
On 26 April 2014 01:13, Kugan wrote:
> What is AArch64 vs. ARM64. Is that something specific to LLVM?
Yes, they're two different AArch64 back-ends, and are being merged
into one official. AArch64 is the one created by Tim at ARM and was
feature complete, while ARM64 is the one created by Apple an
On 26/04/14 03:08, Renato Golin wrote:
> == Progress ==
>
> * Holidays (3 days)
> - Clearing emails/tasks backlog
> - Some post-trip illness
>
> * AArch64 vs. ARM64
> - Comparing performance of both back-ends
What is AArch64 vs. ARM64. Is that something specific to LLVM?
Thanks,
Kugan
>
>
== Progress ==
* Holidays (3 days)
- Clearing emails/tasks backlog
- Some post-trip illness
* AArch64 vs. ARM64
- Comparing performance of both back-ends
* Named Register
- Re-implementing after code review
- http://reviews.llvm.org/D3261
* Time
- CARD-1246 4/10
- Others 6/10
== Plan
Summary:
* Enhance Linaro crosstool-ng.
Details:
1. Work with Bero to release 4.8 binary build.
2. Update Linaro crosstool-ng to use ISL/CLooG for 4.8 build (lp:1172595).
3. Rebase conditional compare experimental codes to lp:gcc-linaro/4.8.
Plan:
* Investigate the impact of conditional compare o
== Issues ==
* None
== Progress ==
* Libunwind AArch64 support:
- Fixed signal frame issue.
- Sent patch upstream for review.
- Delivered patch to OE team for early testing.
* LRA on ARM and AArch64:
- Start to look at what is missing.
== Plan ==
* 3 days off next week
* Continue on L
== Progress ==
* Benchmarks
- Running EEMBC on a Panda
- LLVM on par with GCC in code size and run time
* Release Planning
- Calxeda busted, delays, but got test-suite running on it
- Bootstrap and test-suite fail with atomic support, investigating
- Preparing a Beagleboard for conscience re
== Progress ==
* Submitted binutils patch for testsuite failure on precise.
* Updated glibc memcpy patch based on feedback.
* Updated binutils IFUNC patch based on feedback.
* Started working on AArch64 IFUNC.
* Submitted a couple of cleanup patches for AArch64 binutils.
== Issues ==
* 2 cards b
Progress
Away last week - nothing to report. Will be in BST + 4:30 timezone
this week.
Plans
* Finish off the VFP addressing modes patch.
* Follow up on iterations idiom patch upstream
* Pursue backporting gnu_unique_object upstream.
* Look at some of the existing blueprints and start discuss
On 28 April 2012 21:34, Zhenqiang Chen wrote:
> Summary:
> * Linaro binary toolchain 2012.04 release.
> * Code size benchmark analysis.
>
> Details:
> 1. Validate and bug fix for linaro binary toolchain 2012.04 release.
> 2. Investigate code size regressions in 4.7
> Find more regression cases du
Summary:
* Linaro binary toolchain 2012.04 release.
* Code size benchmark analysis.
Details:
1. Validate and bug fix for linaro binary toolchain 2012.04 release.
2. Investigate code size regressions in 4.7
Find more regression cases due to loop invariant hoisting, and tests
should we can reduce
19 matches
Mail list logo
