== Progress ==
* AARCH64 testing
Drilling down Boot strap failure with GCC 4.9 trunk on open embedded
image with V8 model
Sent the steps to reproduce boot strap failure in the model to team.
Renoto suggestion to add libgcc_eh.a explicilty is not working well at
all places.
Trying few other options (LDFLAGS, --with-stage1-libs ) to pass
libgcc_eh.a to the xg++ build.
* libssp support for Aarch64
Wrote down the steps needed to implement the support in Aarch64. Sent
mail to Matt for a review.
Working on machine descriptions for stack_protect_set and stack_protect_test.
* Filled online VISA Application form. Collected Relevent documents needed.
Hotel rooms are not available via online booking. Sent follow up mail
to the hotel and informed James and Arwen.
== Plan ==
* Continue bootstrap testing and push patches to GCC
* Implement Libssp GCC back end hooks.
* Linaro connect travel prep, book tickets hotel and apply visa.
== Progress ==
* Did builds of GCC 4.6, 4.7, 4.8, 4.9-svn on x86_64, i686, arm7l to
load more recent data into testing database plus test source builds
for the release at the same time.
* Did builds of GDB 7.6 & 7.5 on x86_64, i686, arm7.
* Added wiki page on how to run DejaGnu in a chroot.
* Cbuildv2 work continuing, works well enough to do the above
builds plus bootstrapping infrastructure.
* Change how the index for the testing database gets calculated,
so it's now possible to delete bogus records without screwing
up existing data when importing.
== Plan ==
* Produce some new graphs with the data from the above builds and
test runs.
* Make GCC & GDB release tarballs.
* Update wiki pages on Cbuildv2, release process.
== Issues ==
* Figure out why make check for GDB fails for everything on
chromebook running 13.04.
- rob -
== Progress ==
* Investigated gdb.threads and gdb.multi failures and submitted patch
to enable tests requiring multiple hardware breakpoints on arm
targets.
* Investigate gdb.base failures and submitted patch to enable
disp-step-syscall.exp for arm targets.
* Investigate gdb.mi and gdb.trace failures, some of problems are
feature requests on arm.
* Investigate gdb.base failures and submitted patch to enable
disp-step-syscall.exp for arm targets.
* Submitted gdb.dwarf2 pending patch.
== Plan ==
* Try to fix remaining gdb failures.
* Generate a fresh copy of gdb test suite results on arm and x86
* Chromebook os update on a faster sd card.
* Add JIRA cards for gdb features missing on arm.
* Follow up on Ireland visa application.
== Progress ==
* Better end of loop counter optimisation
- Experimented with fixing the extra instruction.
- Found a possible way to fix it. Discussing it with Christophe.
* Generate a single call to divmod
- Looked at the code including how sin()/cos() -> sincos() handling
in gcc.
- Implemented a prototype and experimented.
== Plan ==
* VRP based zero/sign extension
- Ping the patch.
* Generate a single call to divmod.
- Finish the prototype implementation and get the regression working
- Discuss in gcc mailing list for a good way to implement and get
consensus with the results from prototype.
== Issues ==
* None
== Progress ==
* Test and send out shrink wrapping improvement patch for review (TCWG-133).
* Update aarch64-none-elf TARGET_CFLAGS to " -g -O2 ".
* Enable aarch64 gdb build for Windows (lp:1187862).
* Investigate conditional compare RTL representation.
- Trying to expand it to cmp_and/cmp_ior like instruction.
== Plan ==
* Continue on conditional compare.
== Planed leaves ==
* June 10-12: Dragon Boat Festival.
== Progress ==
* Fixed gdb.cp testsuite failures and committed upstream.
* Worked with ITS to get git mirrors for libraries & tools.
* Started documenting branch and merge policy on the wiki.
* Respin AArch64 binutils ifunc patch and commit.
* Looked into AArch64 assembler issue.
* Assorted other 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
`== Progress ==
* Release 3.3
- Testing and packaging RC3
http://llvm.org/pre-releases/3.3/rc3/
* Bootstrap Script
- Check dependencies, checkout sources, bootstraps, test-suite, package
- Works well on Intel (1h20min bootstrap twice + test-suite)
- Works on Claxeda, Chromebook (10hs each)
- Should work out-of-the-box anywhere:
http://people.linaro.org/~rengolin/llvm/scripts/
* Buildbot
- Following up on GCC/LD failure on linaro-panda-02
* CBuild
- Adding Clang/Extra/RT to toolchain64.lab + update scripts, waiting for
merge
- Hopefully next build will get the whole pack
* Phoronix
- Setting up environment on my Chromebook, I'll have to think how to do
that automatically
- Running some base runs (gcc 4.6), still not automatic enough
* LLVM administrativia
- Reviewing patches, support, etc
== Issues ==
* Network QoS is required to run buildbots, many failures due to timeout
every week. The more bots we run, the more urgent will be this issue.
== Plan ==
* Find a way to run Phoronix without human interaction (batch mode), and
write a script to do that
* Store the base runs somewhere (people.linaro?) and have the script
install them to compare with any run on the board.
* Test and release 3.3 Final
* Use GCC 4.8 on linaro-panda-02 and hope to solve the problem
* Finish LLVM+Clang change in CBuild (merge pending) and try to run some
benchmarks with it
* Think of a way to put bootstrap & phoronix in LAVA/CBuild (whatever is
easier), so I can use the calxeda nodes without worry if they'll be up or
down
Hi,
I am looking at best approach for
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43721 - Failure to optimise
(a/b) and (a%b) into single __aeabi_idivmod call in ARM architecture
In sumary, the following c code results in __aeabi_idivmod() call and
one __aeabi_idiv() call even though the former already calculates the
quotient.
int q = a / b;
int r = a % b;
return q + r;
My question is what would be the best way to handle it. As I see there
are few options with some issues.
1. Handling in gimple level, try to reduce the operations to equivalent
of this. We should do this for the targets without integer divide.
{q, r} = a % b;
Gimple assign stmts have only one lhs operation (?). Therefore, lhs has
to be made 64bit to signify return values of R0 and R1 returned
together. I am not too sure of any implications on other architectures here.
2. Handling in expand_divmod. Here, when we see a div or mod operation,
we will have to do a linear search to see if there is a valid equivalent
operation to combine. If we find one, we can generate __aeabi_idivmod()
and cache the result for the equivalent operation. As I see, this can
get messy and might not be acceptable.
3. An RTL pass to process and combine these library calls. Possibly
using cse. I am still looking at this.
4. Ramana tried a prototype to do the same using target pattens. He has
ruled this out. (if you want more info, please refer to at
https://code.launchpad.net/~ramana/gcc-linaro/divmodsi4-experiments)
Any suggestion for best way to handle this?
Thanks,
Kugan
Hi all,
I am facing build error, when I try to bootstrap GCC trunk for native
aarch64-unknown-linux-gnu configuration in openemedded/V8 model.
Linker error occurs while building stage 1 GCC.
(Snip)
/usr/lib/gcc/aarch64-oe-linux/4.7.3/../../../../aarch64-oe-linux/bin/ld:
gcov: hidden symbol `__deregister_frame_info' in
/usr/lib/gcc/aarch64-oe-linux/4.7.3/../../../aarch64-oe-linux/4.7.3/libgcc_eh.a(unwind-dw2-fde-dip.o)
is referenced by DSO
/usr/lib/gcc/aarch64-oe-linux/4.7.3/../../../../aarch64-oe-linux/bin/ld:
final link failed: Bad value
collect2: error: ld returned 1 exit status
(Snip)
The steps to reproduce the issue is attached.
Need some help to solve this.
regards,
Venkat.
== Progress ==
* Neon intrisincs: compiled my testsuite with GCC/trunk and filed
bugzilla 57431 for ICE.
* Merges for linaro-4.8-2013.06: started actual merges
- fixed a cbuild reporting problem
- faced calxeda and e2c problems, fixed by Matt.
* Jira: a few updates
* Libsanitizer: patched upstream, to be backported in GCC/trunk, then
in gcc-linaro-4.8.
== Next ==
* Merges for linaro-4.8-2013.06: complete them.
* Disable-peeling: resume
* Look at Kugan question about trunk regression
* Libsanitizer/aarch64: resume
* PGO/LTO/python bug: resume
* Neon intrinsics/vzup/vero: resume
== Progress ==
* Investigated attach to process and threads failures
(TCWG-95<http://cards.linaro.org/browse/TCWG-95>).
Almost all problems were fixed with any patch by making an os configuration
change on chromebook.
* Ran GDB test suites after OS configuration change on chromebook and
updated test results.
* Investigated inline-break.exp test suite failures on arm. GDB seems to be
missing one inlined instance on two different functions. Obtained debug
info and dumps of obj file without any luck to find the possible cause and
fix.
* Started work on integration of different testing scripts. Initially added
commandline options in bash script to test let user choose target/host,
native-none/native-gdbserver/remote, and testsuite/testcase configurations.
== Plan ==
* Figure out a reason/solution for inline-break.exp failures on arm.
* Investigate and Fix more ARM bugs shown in gdb 7.6 testsuite results.
* Chromebook os update on a faster sd card.
* Side activity work on automation of testing gdb in different
configurations and uploading comparison result.
== Issues ==
* None.
== Progress ==
* LRA on ARM and AArch64:
- Tried to workaround the issue with new insns (reload_outdi,...).
- But it doesn't seem to be handle by LRA.
- Debug still ongoing.
* Internal meetings
== Plan ==
* Releases merge reviews
* LRA
== Progress ==
Very short week (monday and wednesday off).
* AARCH64 testing
Got boot strap failure with GCC 4.9 trunk on open embedded image with
glibc changes. Retired with latest openembedded image on V8 model
Noted down the steps to reproduce boot strap failure in the model for
broadcasting.
* libssp support for Aarch64
Read documentation to understand and evaluate the work.
== Plan ==
* Continue bootstrap testing and push patches to GCC
* Implement Libssp GCC back end hooks.
* Linaro connect travel prep, book tickets hotel and apply visa.
== Progress ==
* VRP based zero/sign extension
- Tested and posted the latest patch
* Better end of loop counter optimisation
- Tree level optimization are optimized in mainline
- Christophe noted a slight change in asm generated from earlier
version
- tracked down the patch causing this and communicated this.
* Generate a single call to divmod
- Looked at expand_divmod to understand how __aeabi_idiv and
__aeabi_idivmod are generated.
== Plan ==
* Better end of loop counter optimisation
- Change the pattern to remove this additional instruction if
necessary.
* Generate a single call to divmod
- Come up with a solution
== Issues ==
* None
== Progress ==
* Shrink wrapping improvement (TCWG-133)
- Call copyprop to optimized the parameter register move instructions.
- Test is ongoing.
* Update aarch64-none-elf toolchain newlib version to 2.0~20130530 (lp:1185711).
== Plan ==
* Collect performance data for TCWG-133.
* Continue on conditional compare.
Best Regards!
-Zhenqiang
== Progress ==
* Monday holiday here too, so went mountain climbing
* Finally fixed Lava token for cbuild
* Dug into EC2 issues, still confused
* Cloned infrastructure files from gcc.gnu.org, which turned out to be
out of date, so updated them to the current releases. That then
required fixing a few minor configure bugs in libppl. Files in
~/cbuild/var/snapshots/infrastructure. Infrastructure libs are
statically linked so they're consistent across platforms.
* Worked on cbuildv2, it now downloads a tarball or does a
bzr|git|svn checkout, configures, compiles, and installs them in
a sysroot as other packages depend on them. Also added a function
to download, build, and install all the toolchain infrastructure
libraries in a sysroot for binutils & GCC to use at build time
https://git.linaro.org/gitweb?p=people/rsavoye/cbuild2;a=summary
* Automated import of all historical test results till running.
Currently
the DB has 137,687,996 test results, 1909 separate test runs of GCC,
and covering 544 versions.
== Plan ==
* Add remote SSH support to DejaGnu for remote testing on
Chromebook. (carried over from this week)
* Figure out the EC2 mess and document it better
* Clone gcc_release.sh script but enhance so a similar process can be
applied to releasing Eglibc, Newlib, and the Binutils.
* Start gearing up for the releases
* Finish cross build and testing support in Cbuildv2, which would
basically eliminate the need for crosstool-ng.
== Progress ==
* 4 day week due to bank holiday.
* Merged binutils arm ifunc changes onto stable branch.
* Worked on getting some git mirrors setup for various toolchain deliverables.
* A certain amount of planning and JIRA card work in preparation for
the next iteration.
* Fixed aarch64_be-* and 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 Working Group, Linaro
[very short week; two days]
Progress:
* misc
** handover from John Rigby: got a QEMU+KVM+AArch64 setup running with
his work-in-progress patchset
** tracked down weird behaviour when ^C'ing qemu on aarch64
to a bug in glibc's getcontext() implementation (it doesn't
clear the PSTATE field and ends up passing a garbage pstate
to the rt_sigreturn syscall)
Plans:
* VIRT-55: talk to Andre about testing; investigate testing migration
using LAVA
* set up a new qemu-linaro tree/branch as our CI/LAVA input [to keep it
separate from our "we release this" tree]
* restart work on upstreaming omap3 patches as part of my generic qemu
maintenance work (will reduce our maintenance burden in the long term)
-- PMM
== Progress ==
* 3.3 Release
- RC2 is out, we'll have an RC3 (critical bug on X86_64/Darwin)
- Adding some docs to the release
* Infrastructure
- Installing Ubuntu on Chromebook, automating bootstrap+test-suite
- Running the test-suite on a BeagleBoard (LLVM 3.2 and 3.3), no
regressions
- Trying to run an LLVM CBuild job
* Buildbots
- Chasing GCC internal failure on self-host bot
- Chasing more MCJIT failures on all bots
== Issues ==
- Upgrading to 13.04 was a big mistake, had to rollback to 12.10 and
re-configure my whole environment
- Office network/power grid is insufficient for the current population,
I'll be working from home from now on
== Plan ==
* Continue with CBuild for LLVM
* Setup continuous build for bootstrap+test-suite
* Automate Phoronix, setup CI
* If CBuild is done, try running benchmarks with LLVM on it
* As hardware become available, set them up as buildbots
We are using the Linaro prebuilt binary 2013.03 toolchain.
We have a program that does a memcpy of 6 bytes and the source and
destination pointers are both 6 byte arrays (through multiple levels of
struct & union etc).
At -O2 we get the memcpy inlined.
The code area in question is:
22840: f8b7 2054 ldrh.w r2, [r7, #84] ; 0x54
22844: f853 1d12 ldr.w r1, [r3, #-18]!
22848: f042 0202 orr.w r2, r2, #2
2284c: 889b ldrh r3, [r3, #4]
2284e: b292 uxth r2, r2
->22850: f8c7 101a str.w r1, [r7, #26]
22854: f8a7 2054 strh.w r2, [r7, #84] ; 0x54
22858: 83fb strh r3, [r7, #30]
2285a: f8da 3000 ldr.w r3, [sl]
And we get an alignment fault at the str.w marked above.
Looking at the types involved and their location in the containing
structures I don't see how the compiler could think that the destination
was word aligned
(I believe it is guaranteed that dest % 8 == 6)
There are no -march -mcpu or -mtune params passed to the compiler. The
code is running in user space on a A15.
Basic question before we look further:
Is the compiler assuming that cp15 SCTLR.A is 0 so that it is free to
generate unaligned loads and stores?
If the answer to the above is "no" we can isolate the code more and
bring it back to the list.
Thanks,
Bill
---------------------------------------
William A. Mills
Chief Technologist, Open Solutions, SDO
Texas Instruments, Inc.
20450 Century Blvd
Germantown MD 20878
240-643-0836
The Linaro Toolchain and Platform Working Groups are pleased to announce
the 2013.05 release of the Linaro Toolchain Binaries, a pre-built version
of Linaro GCC and Linaro GDB that runs on generic Linux or Windows and
targets the glibc Linaro Evaluation Build.
Uses include:
* Cross compiling ARM applications from your laptop
* Remote debugging
* Build the Linux kernel for your board
What's included:
* Linaro GCC 4.8 2013.05
* Linaro GDB 7.6 2013.05
* A statically linked gdbserver
* A system root
* Manuals under share/doc/
The system root contains the basic header files and libraries to link your
programs against.
Interesting changes include:
* gcc 4.7 is no longer included
* gdb is updated to 7.6
* Linux release file names no longer include a date to make life easier
for scripted downloads
* ISL/CLooG support is enabled in all builds
The Linux version is supported on Ubuntu 10.04.3 and 12.04, Debian 6.0.2,
Fedora 16, openSUSE 12.1, Red Hat Enterprise Linux Workstation 5.7 and
later, and should run on any Linux Standard Base 3.0 compatible
distribution. Please see the README about running on x86_64 hosts.
The Windows version is supported on Windows XP Pro SP3, Windows Vista
Business SP2, and Windows 7 Pro SP1.
The binaries and build scripts are available from:
https://launchpad.net/linaro-toolchain-binaries/trunk/2013.05
Need help? Ask a question on https://ask.linaro.org/
Already on Launchpad? Submit a bug at
https://bugs.launchpad.net/linaro-toolchain-binaries
On IRC? See us on #linaro on Freenode.
Other ways that you can contact us or get involved are listed at
https://wiki.linaro.org/GettingInvolved.
Hi,
I have a usecase where linaro toolchain is used to build my executables and
the sysroot is copied and used as glibc for running my embedded system.
Reason for this is, I want to use the same glibc what the application is
compiled against.
I found a bug fix from glibc community which I want to cherry pick and
rebuild the sysroot to include this fix. But, in the README.txt published
with linaro toolchain binary, there are no instructions for rebuilding
sysroot.
Can anyone point me to info on rebuilding sysroot? If formal steps don't
exist, could you point me to the current process being followed by linaro
so that I can observe the build log and attempt to do the same?
Thanks
Bharath
All,
In the Toolchain Working Group Mans has been doing some examination of SPEC
2000 and SPEC 2006 to see what C Library (glibc) routines impact performance
the most, and are worth tuning.
This has come up with two areas we consider worthy of further investigation:
1) malloc performance
2) Floating-point rounding functions.
This email is interested with the first of these.
Analysis of malloc shows large amounts of time is spent in executing
synchronization primitives even when the program under test is single-threaded.
The obvious 'fix' is to remove the synchronization primitives which will
give a performance boost. This is, of course, not safe and will require
reworking malloc's algorithms to be (substantially) synchronization free.
A quick Google suggests that there are better performing algorithms
available (TCMalloc, Lockless, Hoard, &c), and so changing glibc's algorithm
is something well worth investigating.
Currently we see around 4.37% of time being spent in libc for the whole of
SPEC CPU 2006. Around 75% of that is in malloc related functions (so about
3.1% of the total). One benchmark however spends around 20% of its time in
malloc. So overall we are looking at maybe 1% improvement in the SPEC 2006
score, which is not large given the amount of effort I estimate this is
going to require (as we have to convince the community we have made
everyone's life better).
So before we go any further I would like to see what the view of LEG is
about a better malloc. My questions boil down to:
* Is malloc important - or do server applications just implement their own?
* Do you have any benchmarks that stress malloc and would provide us with
some more data points?
But any and all comments on the subject are welcome.
Thanks,
Matt
--
Matthew Gretton-Dann
Toolchain Working Group, Linaro
Greetings,
I'm using the Linaro tool chain with Eclipse (Juno) (under Windows) and
openOCD to write firmware for an STM32F20x based design (using an ST-Link2
debugger).
In general, that all works fairly well.
The part I'm having problems with is debugging (step-in, etc) from Eclipse.
The execution flow seems chaotic when single stepping through C code: it
skips statements, it jumps into the middle of a function, then returns to
the start of a function, it loops over certain statements (while there's no
loop in the code), etc. (It's close to useless).
I have seen this behavior with other IDE's and tool chains when code was
built with optimization turned on.
However, I specify 'no optimization' (-O0) when I build my code.
My questions:
a) Is there some implicit optimization being done in the compiler, even
though I tell it not to do so, which may affect proper debugging?
b) Are other people using Eclipse (Juno) and are they seeing the same
issue? Are there any known ways to fix this chaotic debugger behavior?
Kind regards,
~ Paul Claessen
== Progress ==
* Performed investigation on gdb7.6 test suite failures and untested test
cases.
* Updated JIRA enteries with test suite failures on arm to track progress.
* Wrote an automation script for selection of individual test cases from a
text file.
* Got the gdb.dwarf2 test suite patch reviewed from Matt and Will.
* Day off on Friday.
== Plan ==
* Finish up initial investigation on gdb7.6 test suite results.
* Complete updates of JIRA enteries after investigation on test suite
results in complete.
* Start work on integration of different testing scripts written in past
couple of months.
* Send gdb.dwarf2 test suite patch upstream.
