== This week ==
- Completed backport of 202259, 202407, 202020, 201261 and 201263
- Submitted merge requesSt for completed backports
== Next week ==
- Begin work on other assigned backports
== Future ==
Document missing features of cbuild for backports
== Progress ==
* Pragma Vectorize
- Comparing pragma OMP to mimic for vectorize
- Implementing the lexer/parser
- http://llvm.org/PR18086
* Android LLVM
- Wasting time for the last time with Odroid XU and Android
- Will focus on Nexus 4, 5 and 7
* Integrated AS
- Changed to enabled by default
- Discussing some bugs found on Android unwind library (inline asm)
- http://llvm.org/PR18231
* Release 3.4
- There were some muddled merges, folks are trying to fix
- Bero found a serious bug, seems to be result of the bad merge
- http://llvm.org/PR18201
- Tested RC2, waiting for RC3
* Background
- Discussions, lots of patch reviews
* Time
- CARD-862 8/10
- Others 2/10
== Plan ==
* Continue implementing pragma vectorize in Clang
* Wait for the next release candidate, test, benchmark
* Follow up in the IAS issues raised
* If RemoteChild is gone by then, continue the MCJIT refactoring
* Have a look at TableGen users
== Issues ==
I saw a black cat, under a ladder, with a hockey mask...
== Progress ==
* Bugfixing and testing QEMU AArch64 FP patches (7/10, VIRT-183)
* Debugging and submitting a patch for issue with Ruby and ARM pointer
encryption (2/10)
* Other miscellaneous work: glibc patch review, binutils testsuite
patch, expenses (1/10)
== Issues ==
* None
== Plan ==
* 2 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
== Progress ==
- cross-validation: (1/10). Follow-up, minor maintenance and
discussions on a few regressions. Now able to share top-level
reports.
- backports (1/10):
* multilib_defaults for 4.7
* committed all approved backport
* helped Michael solve some conflicts
- disable peeling: (3/10)
* confirmed it is now done by default on trunk, as part
-fvect-cost-model=XXX.
* Looked at benchmarks, comparing
-fvect-cost-model=cheap (default) and
-fvect-cost-model=unlimited.
- benchmarks on trunk (1/10): observed some variations from one month to
another on a few cases (checked June-November). This confirms
the need to run benchmarks regularly on trunk, in addition to
release branches.
- cbuild2 (3/10): continued working on source release. Submitted a few
small patches for review+integration.
- misc (1/10): various conf-calls and meetings.
== Next ==
- Make 2013.12 releases
- cbuild2: continue testing, try to make 4.7 source release
- libsanitizer on AArch64: resume work
== Issues ==
* Tcpanda03 seems unusable.
== Progress ==
* LRA on AArch32:
o TCWG-345 : Analyse performance of LRA for ARM. (5/10)
- Installed Saucy on Chromebook, lot of time wasted due to defective SD card
- Frequency governor now set to performance.
- Benchmark setting ongoing
- Tcpand03 SSH access re-enabled, board setting seems ok, but respawned
benchmarks are stuck and the board is no more reachable
o TCWG-343 : Make LRA the default for the ARM backend (2/10)
- Reduce iWMMXT testcase, analysis ongoing.
- Trunk testsuite with LRA shows a couple new faillures.
* Reviewed some merge requests. (1/10)
* Loop specialization patch review started. (1/10)
* Various meetings. (1/10)
== Next ==
* Continue LRA, merge and patch reviews.
== Progress ==
* Updated, tested and submitted new patches for a couple of gdb
testsuite failure on arm. [TCWG-269] [TCWG-34] [1/10]
* Performed GDB git repository testing suite results comparison:
[TCWG-34] [2/10]
Compared results and prepared googldocsheets for the following:
arm-native Vs arm-remote
arm-native Vs x86-native
arm-remote Vs x86-remote
* Investigated difference/failures in arm-native vs arm-remote
comparison sheet. [TCWG-34] [5/10]
Re-ran timeout failures with different values of timeouts.
Figured out causes of failures.
Figured out why some tests exit without emitting any logical result.
* In response to comments upstream tried to figure out alternate fix for
dwarf2 fortran parameter test. [TCWG-267] [TCWG-34] [1/10]
* Miscellaneous activities [1/10]
== Plan ==
* Analyze new failures in arm-native Vs x86-native and arm-remote Vs
x86-remote test results.
* Fix test suite failures and submit patches if any.
* Spend some time pining/updating/re-submit previous patches.
== Progress ==
- libssp gcc
Initiated mails for upstream discussion on supporting global and TLS
based libssp ABI for Aarch64. Now waiting for feedback from ARM
maintainers.
- Built few benchmarks with Linaro tool chain binaries. Faced some
openmp failures, compiler disabled for libgomp. Looking to rebuild
the linaro cross tool chain.
- Rebased glibc trunk and ran cross glibc tests on V8 foundation
model. With TLS SSP patch glibc's libresolve.so fails to build
because the stage 1 GCC compiler emits global stack_chk_guard. The
glibc dos not export global stack_chk_gaurd, when TLS based stack
guard is set. Now looking at supporting and test both TLS and global
stack guard ABI, but before that waiting for confirmation from ARM
maintainers.
- Reinstalled linux 13.04 ubuntu on my laptop
- Tested the patch
http://gcc.gnu.org/ml/gcc-patches/2013-12/msg00170.html for
aarch64-none-elf target. No regressions found.
== Plan ==
- Continue upstream discussions and post RFC patches for glibc and gcc libssp
- Explore on cbuildv2
- Cross Build few openmp benchmarks
== Issues ==
* None.
== Progress ==
* 1.5 days off.
* Misc update for Linaro crosstool-ng
- Re-enable parallel build for do_cc_core.
- Add linaro-armeb-none-eabi config.
- Update all CT_TOOLCHAIN_PKGVERSION to "Linaro GCC 2013.11"
* Share toolchain binaries configures to cbuild2 group.
* Backporting r200103 and r205509 to linaro 4.8.
* Collect Spec2k INT results with -fno-move-loop-invariants and
-fira-loop-pressure on X86-64 and ARM Chrome book. Performance of
different cases waves from -2% - 2%. But the overall performance
changes < 0.5%.
== Plan ==
* Continue on CCMP.
== Progress ==
* Setup new git mirror of new binutils-gdb.git repository, and
added a cron job to update it every 10 minutes. (#369, .5/10)
* Started modifying Cbuildv2 to use new binutils-gdb
repository, which changes how we parse URLs. (.5/10)
* Modified Cbuildv2 to produce fully statically linked binaries so
32bit ones run on any distro, including 64 bit. (#368, 3.5/10)
* Worked with LAVA team to set up a private Jenkins for TCWG use
only to protect test and benchmark data. (#379, 2/10)
* Fixed Cbuildv2 bug where the dryrun function wasn't properly
trapping configure and build errors. (.5/10)
* Meetings & Card maintainance. (2/10)
* Quick winter camping trip at the hot springs for my bday, hit -38C !
== Plan ==
* More tweaks to source and binary tarball creation.
* Finish modifying Cbuildv2 to use new binutils-gdb repository.
* Fix all the minor bugs caused by properly trapping errors from
dryrun function.
* Make the new Jenkins build in a 32 bit chroot on the TCWG build
machines
* Figure out why Jenkins doesn't import the Junit files.
* Copy .sum files to remote host.
* If new Arndale or APM boards arrive this week like promised,
start evaluating them.
* Get the S&M team to start using Gerrit for merge requests for
Cbuildv2.
== Progress ==
* TCWG-367 drop --dostep, add --checkout (1/10)
Completed with following git commits:
commit 2d4d7588c1b05801ee5e1a924c8641ff7c322c07
Author: Ryan S. Arnold <ryan.arnold(a)linaro.org>
Date: Fri Dec 6 11:46:40 2013 -0600
cbuild2.sh: remove --dostep. It's no longer supported.
Also added testcase to make sure it returns an error.
Author: Ryan S. Arnold <ryan.arnold(a)linaro.org>
Date: Fri Dec 6 10:57:34 2013 -0600
Add cbuild2 --checkout <package>|all support with tests
* misc (1/10)
commit 9fb1c4404f8065ef844154e614ff4e7086fce176
Author: Ryan S. Arnold <ryan.arnold(a)linaro.org>
Date: Thu Dec 5 12:21:20 2013 -0600
lib/package.sh: git status should be run in the current directory.
commit 7bb4a9ce8ef440655fe45e6819b57da8d61e8728
Author: Ryan S. Arnold <ryan.arnold(a)linaro.org>
Date: Wed Dec 4 11:47:56 2013 -0600
lib/package.sh: git st should be git status.
* TCWG-356 Unify GIT URL parsing (5/10)
* TCWG-359 Change branch character (2/10)
Closed with following git commits:
commit c9368930e6fb1ad46d08c2dbcc34d8167344ad28
Author: Ryan S. Arnold <ryan.arnold(a)linaro.org>
Date: Tue Dec 3 16:29:00 2013 -0600
Finish git parser refactoring, use stamp functions, complete
dryrun wrapping.
commit eabbc74e48bc8c3a4addbc53ec6a492521193a0c
Author: Ryan S. Arnold <ryan.arnold(a)linaro.org>
Date: Wed Nov 27 16:31:20 2013 -0600
Working additions for git parser refactor and stamping.
== Issues ==
*misc (1/10)
- Discovered a bug in glibc when using upstream (4.9) gcc that isn't
present in 4.8. This might have something to do with how binutils
interacts with the compiler instead of simply a compiler issue:
elf/dl-addr.c:152: multiple definition of `_dl_addr_inside_object'
elf/dl-open.c:746: first defined here
== Plan ==
* Create card for new glibc multiple definition problem,
* Start working on glibc related cards
== This week ==
- Completed backport of 197997
- Completed backport of 203774
- Worked on GCC 4.8 FSF Release Branch Merge and initiated merge request
and build
== Next week ==
- Work on GCC 4.7 Release branch Merge
- Begin work on other assigned backports
== Future ==
Document missing features of cbuild for backports
== Progress ==
* MCJIT (2/10)
- Disabling Remote MCJIT for now, just to add the self-hosting bot
- Working on a more robust message passing interface
- http://llvm.org/bugs/show_bug.cgi?id=18057
- Progress stalled, waiting for changes to child process handler
* Buildbots (2/10)
- Adding Chromebook self-hosting buildbot
- http://lab.llvm.org:8011/buildslaves/linaro-chrome-02
- Adding Odroid XU check-all buildbot
- http://lab.llvm.org:8011/buildslaves/linaro-odroidxu-01
* Vectorizer (2/10)
- Implemented #pragma vectorize enable in LLVM
- http://llvm.org/bugs/show_bug.cgi?id=18086
- Adding support in Clang to add metadata to IR for all three pragmas
* Android (1/10)
- Trying LLVM kernel on XU again
- Managed to get adb/astboot to work
- Custom kernels won't boot, Tinti will create a full image (CM+LLVM)
* Release 3.4 RC2 (1/10)
- Testing, no regressions
- Some benchmarking regressions, investigating
- http://llvm.org/pre-releases/3.4/rc2/
* Background (2/10)
- Reviewing patches, discussions, meetings, etc
== Plan ==
* Continue implementing pragma vectorize on Clang
* Further release 3.4 testing and benchmarking
* Continue investigating benchmark results for 3.4
* Re-start MCJIT MPI once changes to the child process handlers are in
Hi,
According the debian bug report [1], it is not possible to use std::future
on armv5 targetting toolchains. This is because libstdc++ will only enable
std::future if ATOMIC_INT_LOCK_FREE > 1. There is no LDREX for armv5 and
older, so this definition is set to ATOMIC_INT_LOCK_FREE when compiling for
ARMv4t or ARMv5.
My impression is that you should be able to use the kernel helpers for
atomic operations in lockfree (?) manner, so the ATOMIC_INT_LOCK_FREE
definition is probably incorrect on older arm archs then?
Riku
[1] http://bugs.debian.org/727621
== Progress ==
* Disable peeling:
- spawned benchmarking jobs using recent trunk and another older
one to check for performance regressions.
- locally generated the code for the same benchmark to analyze the
differences
* cbuildv2:
- retried to create 4.8-2013.11 source release. Identified a couple
of minor issues, reported to Rob.
- for 4.7-2013.11, need support for subdir in git URLs, fix on-ongoing by Ryan
* Backports:
- gave some support to Michael
- a few have been reviewed/accepted.
* libsanitizer: little progress this week; advised to take a look at
recent LLVM sources.
* trunk validation: filed some bugzilla reports; 2 of them fixed by Kyrill.
== Next ==
* Disable peeling:
- check benchmarks results
- check code generation
* cbuildv2: re-do source releases 4.8 and 4.7 2013.11
* Backports:
- commit already approved ones, once cbuildv2 releases are OK
- see which ones can be easily added
- work on MULTILIB_DEFAULTS backport for 4.7
== Issues ==
* None.
== Progress ==
* LRA on AArch32:
o TCWG-342 : UPSTREAM: LRA issue in gfortran with store minmaxsi
- Committed as rev205526 .
- Card resolved.
o TCWG-344 : UPSTREAM: Thumb bootstrap failure with LRA
- Committed THUMB_SECONDARY_INPUT_RELOAD_CLASS patch as rev205527.
- Committed PR58785 patch as rev205581.
- Card resolved.
o TCWG-345 : Analyse performance of LRA for ARM
- Gathered results and analysis still ongoing.
o Working on a new failure with iWMMXT (LRA loops during constraints solving).
* Reviewed some merge requests.
== Next ==
* Continue on LRA
* Loop specialization patch review.
== Progress ==
* Investigated remaining testsuite failures in ARM process record/replay.
* Tested VFP, SIMD and other advance instruction types recording.
* Ran GDB testsuite in various configurations on gdb7_6_1 code base
and latest git repo.
* Learnt some prologue and epilogue analysis heuristics for resolving
process record bugs in arm.
== Plan ==
* Analyze test results from gdb testsuite runs in various configs and
update JIRA issues.
* Complete testing of VFP, SIMD and other advance instruction types
recording patch and Send updated patch.
* Try to find a epilogue analysis heuristics for resolving reverse
stepping issues in solib code.
== This week ==
- Completed backport of 202872
- Final checkin to upstream GCC SVN will be complete by Christophe Lyon
== Next week ==
- Begin work on other assigned backports
== Future ==
Document missing features of cbuild for backports
== Progress ==
- libssp gcc
Posted RFC V2 patch to community. Updated comments from Richard and
wating for some feed backs.
- Libssp glibc
- Sent out a patch for stack_chk_guard in Aarch64 along with TLS
stack guard support.
== Plan ==
- post RFC patches for glibc and gcc libssp
- explore on cbuildv2
29-11-2013 Friday - Leave (AMD internal event) .
== Progress ==
* Setup 64 bit centos-5 and suse-10 chroots for testing binary
tarballs, and used them to verify the Cbuildv2 produced ones
compile 'Hello World!", and run on a real target.
* Got remote chromebook testing working in TCWG build farm.
* Worked on getting GDB remote testing with gdbserver working.
* Did build and test run on aarch64 APM board of GCC
linaro-4.8-branch.
* Changed Cbuildv2 to disable parallel make jobs when building GCC
native on ARM or AARCH64 platforms, as the hardware can't handle
the load.
* Got the LSB tools installed and researched what they do.
* Debugged why 32 bit binary tarballs made in a chroot won't run
when installed on multiple x86_64 systems. Works now by statically
linking everything.
* Got test results, converted to Junit format for Jenkins.
* More TCWG build farm admin issues.
== Plan ==
* Continue working on GDB remote testing in the build farm.
* More tweaks for binary releases.
* Continue trying to get GCC trunk to build on APM board.
* Figure out why Jenkins doesn't import the Junit files.
* Probably more TCWG build farm admin issues, which is probably
a continuing task, so I'll stop listing it every week.
== Issues ==
* If I try to monitor a Jenkin's build via the "Console", it
crashes my browser as the logs get huge.
* Long weekend for Thanksgiving holiday means short work week...
== Leave ==
* Off this coming Thursday for my birthday...
== Progress ==
- cbuild2 benchmarking
- Resolved access issues and imported into repository
- continuing with the missing implementations
- 64bit division for ARMv7-A
- Algorithm is committed to trunk
- enablement patch is posted for review
- trunk bootstrapping issue
- Setup foundation model and resolved space and kernel panic issues
- There is a assembler compatibility issue with older assembler
(-mabi=lp64); trying with the latest binutils
- AARCH64 bootstrapping in progress with this
- AARCH32 bootstraps with glibc but ran into issues with eglibc.
== Plan ==
- Address zero/extension review comments
- investigative bootstrapping issues
- continue with cbuild2 benchmarking
== Issues ==
* None.
== Progress ==
* Commit the fix for test case (lp1243022.c) by skipping arm-neon.
* Spawn arm-none-eabi build for Linaro 2013.11 release.
* Report PR59282: SPEC2K 252.eon ICE.
* Rebase conditional compare patch to trunk and tests.
- Update simplify_while_replacing to skip swapping compare in
conditional compare.
- Check whether operands of gen_ccmp_next clobber cc or not.
- Add a short description about the over all algorithm.
* Investigating loop-invariant impact on SPEC2K INT for x86-64 and
ARM. Testing is ongoing,
== Plan ==
* Continue on CCMP.
== Planed leaves ==
* Dec 3 & 5: Annual leaves
== Progress ==
* Buildbots
- Work-around for ClamAV (r195646), new bot in!
- http://lab.llvm.org:8011/buildslaves/linaro-chrome-03
- After a week stable, I'll deactivate the old chromebook and re-fit it
- Looking at MCJIT random breakages on A15 self-hosting tests
- http://llvm.org/PR18057
- Proposed a fix, http://llvm-reviews.chandlerc.com/D2287
- Installed Arch on the ODroid XU, running a local buildbot on it
- Investigating llvm-rtdyld but in reading debug information
- http://llvm.org/PR18085
* Vectorizer
- Mapping, discussing and proposing implementation for pragmas
- http://llvm.org/PR18086
- http://llvm-reviews.chandlerc.com/D2289
* Release 3.4 RC1
- Running benchmarks comparing 3.3 with 3.4
- EEMBC within noise levels for geomean
- O3: ~0.2% faster, ~0.7% bigger
- Os: ~1.3% slower, ~0.6% bigger
- Phoronix, ImageMagick: OK within std dev
* LLVMAndroid
- Tinti compiled the kernel 3.4 and some libs with LLVM
- Trying to put Android on the ODroid XU (the official one is quite poor)
- XU redirected to set as a buildbot, once ready, I'll use the other
for Android
* Background
- Lots of patch reviews, discussions
- Helping Graphics WG with Clover
== Issues ==
Still ill because of implant, on/off throughout the week.
== Plan ==
* Put the self-hosting bot up once it's fixed
* Fix the XU bot
* Try LLVM Android on XU again
* Continue with the simple vectorization pragmas
* Waiting on benchmark test-suite mode to create a new benchmark test-suite
== Progress ==
* lib/git-parser.sh: Add support for ~ as branch designator and
multi-/ branches.
* Refactor cbuild2 to use git parser
* Created stamp functions for cbuild2
US Thanksgiving Holiday
== Next ==
* Finish refactor of cbuild2 to use git parser.
* Create unified parser that wraps git parser.
* Finish refactor of cbuild2 to use stamp functions.
== Issues ==
* None
Forgot to hit send on this one
== Progress ==
* Add documentation for git-parser.sh.
* lib/git-parser.sh: Add no-url support.
* testsuite/test.sh fix invocation of testsuite/git-parser-tests.sh
to include ${topdir}.
* Add lib/git-parser.sh and testsuite/git-parser-tests.sh.
* Fix corner cases with <user>@<url>/<repo>.git[/branch]@<revision>
1) Allow http urls to be processed by 'git' cases.
2) Error check git-new-workdir and git checkout
3) Parse revision and branch properly when there might be a <user>@
in the url.
* testsuite/test.sh: Update for breath to cover
user@<url>/<repo>.git@<revision>
* Fix get_srcdir to work with <user>@<repo>.git/branch@revision
* Fix get_toolname and get_srcdir when using <user>@<repo>.git@revision
== Issues ==
* None
== Next ==
* Have cbuild2 start using the git parser
== Issues ==
* Still some cbuild oddities.
== Progress ==
* LRA on AArch32:
o TCWG-342 : UPSTREAM: LRA issue in gfortran with store minmaxsi
- Performance validation is OK, confirmed by kyrill.
- Waiting for approval.
o TCWG-344 : UPSTREAM: Thumb bootstrap failure with LRA
- Pinged for THUMB_SECONDARY_INPUT_RELOAD_CLASS patch review
- Validate and post patch for PR58785:
http://gcc.gnu.org/ml/gcc-patches/2013-11/msg02459.html
o TCWG-345 : Analyse performance of LRA for ARM
- Analysing results mismatch between 2 pandas
- Configured and ran spec2000 on Chromebook
- Analysis ongoing
== Next ==
* Continue on LRA
* Reviews
== Progress ==
* Released GCC 4.7 and 4.8 2013.11 releases.
* Investigated potential regressions on trunk, as reported by
continuous cross-validation.
Reported some cases to Kyryll. Another, reported to Bin, turns out
to be an unrelated, unstable testcase recently introduced.
Will have to give a closer look at big-endian tests.
* Updated libsanitizer patch for AArch64. It builds again but is not
functional yet (running in the Foundation model currently); getting
support from libsanitizer developers. Support for AArch64 will have to
be committed in LLVM, and merged into GCC later. I'm going to continue
prototyping under GCC though, and will submit changes to the
libsanitizer team when ready.
* GNU tar regression (extended_negsidi pattern): posted bugzilla,
fixed by Richard.
* cbuildv2: gave another try, pointing to staging.g.l.o, to discover
that it was outdated too. Rob has fixed it since then.
* Backports: gave some support to Michael Collison to help him get to speed.
Prepared backport of Zhenqiang's "enhance phiopt
to handle BIT_AND_EXPR" (TCWG -303)
== Next ==
* Resume "disable-peeling" work. Mostly check that the current trunk
contains what we want.
* cbuildv2: retry to create source release 2013.11
* Backports: commit TCWG-303, and Charles' backport of his testsuite fix
look at the others in the list.
* libsanitizer for AArch64: make it functional
== Progress ==
* GDB ARM Process Record:
- Completed work on arm process record Advance SIMD, vfp and coprocessor
instruction recording.
- Submitted initial patch for SIMD. VFP and coprocessor instruction
decoding.
- Resubmitted previous patches after incorporating suggestions.
- Resolved patch line wrap issues and formating issues.
* Macau visa and travel planning
* Got started with using concur
== Plan ==
* GDB ARM Process Record:
- Follow up on previous patches.
- Test VFP, SIMD and other advance instruction types recording.
- Fix issues and submit their fixes if any.
* Run GDB testsuite in various configurations and analyze failures.
== Progress ==
* Created 32 bit chroots on all 6 TCWG build machines, did test
toolchain builds via Cbuildv2, including a Canadian cross. I
tested the win32 executables with wine and they work.
* Setup all 6 TCWG build farm chromebooks to be able to do native
builds and run tests with Cbuildv2.
* Multiple discussions with LAVA team about Jenkins, Gerrit, LAVA,
and GIT repositories. We need to have LAVA & Jenkins installed on
our new x86_64 build machines in a way they can do builds in a
32 bit chroot.
* Got Gerrit working with GCC and Cbuildv2 GIT repositories on
staging.git.linaro.org, and merge requests ala 'git review' now
work and can get approved. (Thanks to Milo)
* Got the GCC git repository on staging to be in sync with upstream
finally, as it wasn't auto updating. (Thanks to Milo)
* Modified Cbuildv2 to get the host and build architectures right
when building in a 32 bit chroot on a 64 bit build machine.
* Fixed other weird issues in Cbuildv2 when building in a 32 bit
chroot on an x86_64 platform.
* Started process to get Kugan access to the APM board for
benchmarking.
* Got Jenkins doing builds and test runs on the new TCWG build
machines.
== Plan ==
* Get back to remote chromebook testing support for build machines.
* Debug why 32 bit binary tarballs made in a chroot won't run when
installed on an x86_64 system.
* Probably more TCWG build farm admin issues.
== Progress ==
- libssp gcc
- Posted RFC patch to community. Addressing gcc/glibc compatibility issues.
- libssp glibc
- Working on exporting stack_chk_guard in Aarch64 along with TLS
stack guard support.
== Plan ==
- post RFC patches (version 2) for glibc and gcc libssp
== Issues ==
* None.
== Progress ==
* Commit the patch to support S2_<op1>_<Cn>_<Cm>_<op2> system register
in AARCH64 GAS.
* Identify the issue files in parallel build fail (PR57683) and
backport r197467 and r198999 to FSF GCC 4.8.
* Verify Linaro crosstool-ng to make sure Fortran is supported in all builds.
* Try PGO build for ifcombine heuristics. But got "the control flow of
function .. does not match its profile data".
* Investigate loop-invariant heuristics and rtx cost to select
SYMBOL_REF. But tests did not show performance gain.
* Investigate Coremark conditional compare issue in Cortext-M since
the BRANCH_COST is 1.
== Plan ==
* Continue on CCMP.
* Discuss ifcombine heuristics with upstream.
== Planed leaves ==
* Dec 3 & 5: Annual leaves
== Progress ==
- cbuild2 benchmarking
- Done the initial frame work (just with one benchmark) and sent out
for review
- 64bit division for ARMv7-A
- Posted the patch and added target hook documentation required
== Plan ==
- Address zero/extension review comments
- post 64bit divide patch with the required documentation
- investigative bootstrapping issues
- still waiting for h/w access
On 21 November 2013 07:12, Karlsson, Magnus <Magnus.Karlsson(a)lsi.com> wrote:
> Just wondering if somebody could point me to a good document on how the heap
> reclamation algorithm works for memory allocated in a user space program
> using the regular malloc/calloc functions.
Section 7.1.3, whose sub-sections include: "Implementation of malloc()
and free()", "Tools and libraries for malloc debugging", and
"Controlling and monitoring the malloc package", of Michael Kerrisk's
"The Linux Programming Interface" (http://man7.org/tlpi/index.html) is
one of the better reads of which I'm aware. He recommends reading the
man pages for malloc_info, malloc_stats, mallopt, and mallinfo (among
others) for more information.
In the C language, reclamation of allocated memory is usually driven
by the application. When you free() some memory, internal structures
know the size of what was previously allocated at the given location
(i.e. what was given to you by malloc()) and simply release that back
into the heap. There are ways to tweak the allocation of memory.
== This week ==
- This week was mostly spent on coming up to speed on the Linaro
backport process
- Backport 202872 - Merged changes from trunk to Linaro branch
== Next week ==
- Complete backport of 202872
- Begin work on other assigned backports
== Future ==
No concrete plans yet.
---------- Forwarded message ----------
From: Mark Pupilli <mpupilli(a)gmail.com>
Date: 17 November 2013 14:07
Subject: condition_variable_any missing from libstdc
To: linaro-toolchain(a)lists.linaro.org
Hi,
I sent this message a week ago but I don't think I was subscribed to the
list correctly. Apologies if it is repeated (it doesn't show in the
archive).
I have a problem with my cross build of (Linaro GCC 4.8-2013.10). I get the
following runtime linker errors regarding condition_variable_any:
"relocation error: /usr/local/lib/librobolib.so: symbol
_ZNSt22condition_variable_anyC1Ev, version GLIBCXX_3.4.11 not defined in
file libstdc++.so.6 with link time reference"
If I examine my built version of libstdc with readelf I get the following
output:
$ readelf -s ./src/.libs/libstdc++.so.6 | grep condition
10383: 000c58d8 68 FUNC LOCAL DEFAULT 11 _ZNSt15error_conditionC1E
10818: 000c58d8 68 FUNC LOCAL DEFAULT 11 _ZNSt15error_conditionC2E
10837: 000c5944 40 FUNC LOCAL DEFAULT 11 _ZNKSt15error_condition8c
10942: 000c591c 40 FUNC LOCAL DEFAULT 11 _ZNKSt15error_condition5v
Where as with the apt-get installed 4.6 version of the toolchain shows:
$ readelf -s /usr/arm-linux-gnueabi/lib/libstdc++.so.6 | grep condition
777: 000523b1 12 FUNC GLOBAL DEFAULT 12
_ZNSt22condition_variable@@GLIBCXX_3.4.11
929: 000522f1 104 FUNC GLOBAL DEFAULT 12
_ZNSt18condition_variable@@GLIBCXX_3.4.11
1037: 000523b1 12 FUNC GLOBAL DEFAULT 12
_ZNSt22condition_variable@@GLIBCXX_3.4.11
1198: 000522f1 104 FUNC GLOBAL DEFAULT 12
_ZNSt18condition_variable@@GLIBCXX_3.4.11
1686: 00052385 14 FUNC GLOBAL DEFAULT 12
_ZNSt18condition_variable@@GLIBCXX_3.4.11
2166: 00052359 12 FUNC GLOBAL DEFAULT 12
_ZNSt18condition_variable@@GLIBCXX_3.4.11
2438: 00052359 12 FUNC GLOBAL DEFAULT 12
_ZNSt18condition_variable@@GLIBCXX_3.4.11
2685: 00052365 16 FUNC GLOBAL DEFAULT 12
_ZNSt18condition_variable@@GLIBCXX_3.4.11
3186: 00052395 26 FUNC GLOBAL DEFAULT 12
_ZNSt22condition_variable@@GLIBCXX_3.4.11
3448: 00052395 26 FUNC GLOBAL DEFAULT 12
_ZNSt22condition_variable@@GLIBCXX_3.4.11
3643: 00052375 14 FUNC GLOBAL DEFAULT 12
_ZNSt18condition_variable@@GLIBCXX_3.4.11
(Which is still missing anything to do with condition_variable_any, but
given that my native 4.8 compiler doesn't contain this symbol either and my
code builds and runs natively, I assume this is how it should be).
Here is my build's version information:
$ arm-linux-gnueabi-gcc -v
Using built-in specs.
COLLECT_GCC=arm-linux-gnueabi-gcc
COLLECT_LTO_WRAPPER=/home/mark/arm-linux-gnueabi-4.8.2/libexec/gcc/arm-linux-gnueabi/4.8.2/lto-wrapper
Target: arm-linux-gnueabi
Configured with: ../gcc-linaro-4.8-2013.10/configure
--target=arm-linux-gnueabi --prefix=/home/mark/arm-linux-gnueabi-4.8.2
--with-local-prefix=/home/mark/arm-linux-gnueabi-4.8.2 --disable-nls
--enable-shared --enable-multilib --disable-decimal-float
--enable-languages=c,c++
--with-mpfr-include=/home/mark/gcc-4.8-arm-linux/gcc-build/../gcc-linaro-4.8-2013.10/mpfr/src
--with-mpfr-lib=/home/mark/gcc-4.8-arm-linux/gcc-build/mpfr/src/.libs
--enable-clocale=gnu --enable-threads=posix --enable-__cxa_atexit
--disable-libstdcxx-pch --with-system-zlib
--with-headers=/home/mark/arm-linux-gnueabi-4.8.2/include
--with-libs=/home/mark/arm-linux-gnueabi-4.8.2/lib
--enable-libstdcxx-threads --enable-libstdcxx-time
Thread model: posix
gcc version 4.8.2 20131014 (prerelease) (Linaro GCC 4.8-2013.10)
I configured libstdc++-v3 respectively as follows:
$ ../gcc-linaro-4.8-2013.10/libstdc++-v3/configure --host=arm-linux-gnueabi
--prefix=/home/mark/arm-linux-gnueabi-4.8.2/ --enable-multilib
--enable-shared --disable-nls --disable-libstdcxx-pch
--enable-libstdcxx-threads --enable-libstdcxx-time
I assumed the relevant entries to enable C++11 threading and condition
variables etc would have been --enable-libstdcxx-threads
--enable-libstdcxx-time. I must be missing some other options or have done
something else wrong. Any suggestions?
thanks,
Mark
== Progress ==
* Short week
- Two days off due to a messy implant bloating my face
- Should be better on Monday
* Cambridge LLVM Day, Cambridge University Computer Lab
- Presented the status of the auto-vectorizer in LLVM
* Releasing candidate 1 of LLVM 3.4
- All tests green, running benchmarks
- http://people.linaro.org/~rengolin/llvm/
* Buildbots
- Adding Chromebook self-hosting (fixing MCJIT tests)
- Adding Chromebook test-suite (fixing ClamAV)
- Will turn off the old Chromebook and re-install it for benchmarks
- Will add an Odroid XU in pair with the community one to be added next
week
* Background
- Patch reviews, discussions
* EEMBC rgbcmy implementation requires extensive changes to the compiler
- Will deal with them on the background over the next months
- While checking other EEMBC problems
== Plan ==
* Continue the 3.4 release
* Look at vectorization pragmas
* Look at other EEMBC results
== Progress ==
* Committed a couple of gdb patches
* Debug malloc to a working state, performance improved
* First version of glibc aarch64 ifunc support
* Found a couple of bugs in binutils aarch64 ifunc support
== Issues ==
* Missed two days due to illness
* Power cut and broadband outage on Wednesday afternoon
== Plan ==
* Respin and submit glibc docs patches
* Submit glibc aarch64 ifunc code
--
Will Newton
Toolchain Working Group, Linaro
Hi, All
Under this site
http://releases.linaro.org/13.09/components/toolchain/binaries/,
there are many files released. but do we have any description on the file
naming rules?
Sorry for my simple question, I just want to know what the files are used
for. which one I should select when I need to use toolchain.
Like the files below, I can guess that aarch64 means that it will generate
files run on aarch64 platform, but I can not guess what's the difference
between linux and none, and not know what's the difference between gnu and
elf.
So if you have any wiki/link about the the naming rules or description
about the file,
please share me.
crosstool-ng-linaro-1.13.1-4.8-2013.09-01.tar.bz2
crosstool-ng-linaro-1.13.1-4.8-2013.09.tar.bz2
gcc-linaro-aarch64-linux-gnu-4.8-2013.09-01_linux.tar.bz2
gcc-linaro-aarch64-linux-gnu-4.8-2013.09-01_linux.tar.xz
gcc-linaro-aarch64-linux-gnu-4.8-2013.09-01_runtime.tar.bz2
gcc-linaro-aarch64-linux-gnu-4.8-2013.09-01_src.tar.bz2
gcc-linaro-aarch64-linux-gnu-4.8-2013.09-01_win32.zip
gcc-linaro-aarch64-linux-gnu-4.8-2013.09-01_win32.zip.xz
gcc-linaro-aarch64-linux-gnu-4.8-2013.09-20130912_win32.exe
gcc-linaro-aarch64-linux-gnu-4.8-2013.09_linux.tar.bz2
gcc-linaro-aarch64-linux-gnu-4.8-2013.09_linux.tar.xz
gcc-linaro-aarch64-linux-gnu-4.8-2013.09_runtime.tar.bz2
gcc-linaro-aarch64-linux-gnu-4.8-2013.09_src.tar.bz2
gcc-linaro-aarch64-linux-gnu-4.8-2013.09_win32.zip
gcc-linaro-aarch64-linux-gnu-4.8-2013.09_win32.zip.xz
gcc-linaro-aarch64-none-elf-4.8-2013.09-01_linux.tar.bz2
gcc-linaro-aarch64-none-elf-4.8-2013.09-01_linux.tar.xz
gcc-linaro-aarch64-none-elf-4.8-2013.09-01_win32.zip
gcc-linaro-aarch64-none-elf-4.8-2013.09-01_win32.zip.xz
gcc-linaro-aarch64-none-elf-4.8-2013.09_linux.tar.bz2
gcc-linaro-aarch64-none-elf-4.8-2013.09_linux.tar.xz
gcc-linaro-aarch64-none-elf-4.8-2013.09_win32.zip
gcc-linaro-aarch64-none-elf-4.8-2013.09_win32.zip.xz
gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09-01_linux.tar.bz2
gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09-01_linux.tar.xz
gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09-01_runtime.tar.bz2
gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09-01_win32.zip
gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09-01_win32.zip.xz
gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09_linux.tar.bz2
gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09_linux.tar.xz
gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09_runtime.tar.bz2
gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09_src.tar.bz2
gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09_win32.zip
gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09_win32.zip.xz
gcc-linaro-aarch64_be-none-elf-4.8-2013.09-01_linux.tar.bz2
gcc-linaro-aarch64_be-none-elf-4.8-2013.09-01_linux.tar.xz
gcc-linaro-aarch64_be-none-elf-4.8-2013.09-01_win32.zip
gcc-linaro-aarch64_be-none-elf-4.8-2013.09-01_win32.zip.xz
gcc-linaro-aarch64_be-none-elf-4.8-2013.09_linux.tar.bz2
gcc-linaro-aarch64_be-none-elf-4.8-2013.09_linux.tar.xz
gcc-linaro-aarch64_be-none-elf-4.8-2013.09_win32.zip
gcc-linaro-aarch64_be-none-elf-4.8-2013.09_win32.zip.xz
gcc-linaro-arm-linux-gnueabihf-4.8-2013.09-20130912_win32.exe
gcc-linaro-arm-linux-gnueabihf-4.8-2013.09_linux.tar.bz2
gcc-linaro-arm-linux-gnueabihf-4.8-2013.09_linux.tar.xz
gcc-linaro-arm-linux-gnueabihf-4.8-2013.09_runtime.tar.bz2
gcc-linaro-arm-linux-gnueabihf-4.8-2013.09_src.tar.bz2
gcc-linaro-arm-linux-gnueabihf-4.8-2013.09_win32.zip
gcc-linaro-arm-linux-gnueabihf-4.8-2013.09_win32.zip.xz
gcc-linaro-armeb-linux-gnueabihf-4.8-2013.09_linux.tar.bz2
gcc-linaro-armeb-linux-gnueabihf-4.8-2013.09_linux.tar.xz
gcc-linaro-armeb-linux-gnueabihf-4.8-2013.09_runtime.tar.bz2
gcc-linaro-armeb-linux-gnueabihf-4.8-2013.09_win32.zip
gcc-linaro-armeb-linux-gnueabihf-4.8-2013.09_win32.zip.xz
--
Thanks,
Yongqin Liu
---------------------------------------------------------------
#mailing list
linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org>
http://lists.linaro.org/mailman/listinfo/linaro-android
linaro-validation(a)lists.linaro.org <linaro-dev(a)lists.linaro.org>
http://lists.linaro.org/pipermail/linaro-validation
Hi toolchain gurus,
I am about to start some projects working with CortexMx devices and am
wondering if anyone has an opinion on which toolchain(s) I should
use/investigate?
Being a fan of Linaro, my first instinct would be to use cbuild2 to
build an arm-none-eabi- toolchain from a 4.8.x tree. But looking
around I can't help notice https://launchpad.net/gcc-arm-embedded.
Does anyone know if gcc-arm-embedded has things the Linaro toolchain
doesn't wrt Cortex M0, M3, and M4 device/instruction support?
Best regards,
Trevor
-------- Original Message --------
Subject: [Bug target/59216] [ARM] negdi*extendsidi regression
Date: Wed, 20 Nov 2013 18:06:14 +0100
From: christophe.lyon at st dot com <gcc-bugzilla(a)gcc.gnu.org>
To: Christophe LYON <christophe.lyon(a)st.com>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59216
--- Comment #2 from christophe.lyon at st dot com ---
Basically, the working code does:
asrs r3, r2, #31
negs r2, r2
sbc.w r3, r3, r3, lsl #1
while the failing one does:
negs r2, r2
asrs r3, r2, #31
--
You are receiving this mail because:
You reported the bug.
Hi LAVA folks,
I don't know if you guys know, but Android is moving to LLVM for the next
release or so. As such, we'll need to do a lot of testing between now and
next release to make sure each component can be compiled (and runs
correctly) with LLVM on an incremental basis.
We're trying to come up with a way for remotely testing the Linux kernel
booting on ARM devices, more specifically an Android stack, and I'm finding
it hard to do that with my home equipment. Doing that in LAVA would be
ideal, and I know the Android team does it already, but our constraints
could be a little different.
Basically, there are two fronts:
1. Building Android components with LLVM, using a GCC-compiled kernel
booting on an ARM board, in LAVA. This is something we should work
internally on how to do it, and it'll be between Android, LAVA and
Toolchain groups.
2. Building the Linux kernel with LLVM, and using a GCC-compiled image
(like stock CyanogenMod) to test the kernel. We don't have such a kernel
(many patches), but the LLVMLinux guys do, and that's where they come in.
On the second case, the topic of this email, we'd have to liaise with them
to fire jobs at LAVA from their own infrastructure (originally, manually
only), and that might need some thinking. But ultimatelly, we want to have
those jobs running on LAVA, so that later on we'd be able to have a third
layer: Linux+Android built with LLVM with the same system level tests.
Since the LLVMLinux guys don't have access to much ARM hardware, and since
it's easier for us to scale (or to re-define) hardware requirements, having
them running on LAVA makes even more sense.
Is this something we can do? Is this being done already? Is this just a
question of legal/corporate decision, or is there any technical issues we
have to look into?
Android folks,
It might make more sense if you guys just grab their kernel and build the
Android system based on that internally, so that we don't need external
access to job submissions in LAVA, but that would mean work from you guys
to patch it up, and that might not be in the roadmap for the next months.
Is that a feasible route?
cheers,
--renato
= Progress ==
* Created Cards for the infrastructure Team TODO list.
* Finished Cbuildv2 support for building GDB binary tarballs.
* Got Arch linux up on Odroid XU board again, seems stable, did a
build and test run.
* Experimented with lava-tool.
* Tried to get GCC trunk building native on aarch64 for libsanitizer
patch testing.
* Upgraded gmp to 5.1.3 in infrastructure/ to work around a configure
bug triggered by crouton native builds on a chromebook.
* Setup chromebook slaves in new toolchain build farm.
* Started adding support to Cbuildv2 to handle git URLs with a user
name, ie.. git(a)staging.git.linaro.org to work around git repo
problem.
== Plan ==
* Finish support for user names in URLs.
* Continue on remote testing support.
* Keep trying gcc trunk on aarch64 native.
* Fix git repo.
== Issues ==
* GCC git repo hasn't been auto updating the svn branch of
linaro-4.8-branch. It used to work... updating manually is now
broken as well.
* Somehow qemu snapshots tarballs are overwriting the toolchain
directories on snapshots.linaro.org.
* I don't think lava-tool is going to be useable for toolchain
testing, as it only queues up an executable test case to be run
later, whereas GCC expects the test to get run right away.
One day off
== Progress ==
* Prepared 4.7 and 4.8 2013.11 releases. Some delay because of board
crashes and disk full issues.
* Aarch64: committed 'frame grows downward' patch. This removes a
dependency for libsanitizer and libssp.
* libsanitizer on Aarch64: blocked by GCC trunk not bootstrapping
currently on Aarch64 HW (reported by Rob)
* Looked at cross-build failures of trunk after new
-fisolate-erroneous-paths. Ramana pointed me to Marcus' glibc patch,
and I could switch my builds from eglibc to glibc.
* cross-validations: updated list of configurations built&tested after
discussion with Richard during Connect.
== Next ==
* Announce 4.7 and 4.8 2013.11 releases
* Continue investigating 'extended neg' fix (aka tar regression)
* Look for patches to fix AArch64 bootstrap, so that we can test libsanitizer
One day off.
== Issues ==
* Various cbuild issues:
- disk full, boards down and benchmarks launched on different boards
== Progress ==
* LRA on AArch32:
- Proposed a ARM backend fix for the Fortran issue
http://gcc.gnu.org/ml/gcc-patches/2013-11/msg01997.html
- Performance analysis ongoing
* Merge reviews and backports.
== Next ==
* Continue on LRA
== Progress ==
* Wrote ARM and Thumb stub handlers for simd, vfp and coprocessor
instruction recording.
* Read documentation on VFP and Neon register set to figure out a register
recording method.
* Follow up on upstream patches.
* Investigating a un-handled instruction test suite failure in arm process
record.
* 9th/10th Muharram Public holiday on Thursday and Friday.
== Plan ==
* Fix failures in arm process record due to un-handled instruction.
* Get started on writing handlers for coproc, vfp and simd instructions.
== Issues ==
* None.
== Progress ==
* One day (Nov. 15) off.
* Misc update for Linaro crosstool-ng
- Use newlib-linaro-2.0.0-2013.11-1.
- Update fortran support related scripts and configs according to
Matt's comments.
* Propose to support S2_<op1>_<Cn>_<Cm>_<op2> system register in AARCH64 GAS.
- Yufeng followed-up it and added full TRACE registers support.
* Investigate heuristic to tune ifcombine (TCWG-313)
- Got some new fails in regression tests since some optimizations
can not get the expected result.
- Collect Spec2k INT result. Overall there is no changes. But there
are -2 - 1% changes for several cases.
- PGO tests are ongoing.
== Plans ==
* Continue on CCMP.
* Continue on ifcombine tuning.
== Progress ==
* Preparing presentation on auto-vec for LLVM
- For Cambridge LLVM Day next Monday
- If accepted, also for FOSDEM 14
* Tracing strided access changes needed in auto-vec (PR17677)
- Reading the paper, preparing a reference implementation
- Discussing details and preparing the LLVM code to introduce it
- After a few attempts, it's clear that the code is not yet ready to cope
with the changes
- I'll have to work on the surrounding code to re-factor it for more
robust integration
- As well as triming some other edges (like pragmas) to help implement it
* Planning Android builds
- Trying to get a reference platform (most likely the new Arndale)
- LLVMLinux folks will help streamlining a kernel package for it
* Connect reservations, booking flight, etc.
- All done!
== Plan ==
* Monday at Cambridge LLVM Day at CUCL
* 3.4 Release testing
* Looking at vectorization pragmas and general structure of the memory
dependency checks
