== Progress ==
* Investigated gdb.dwarf2 unsupported issues wrote two new patches for
gdb.dwarf2 testsuite.
* Read some background on dwarf2 to translate test written in x86
assembly into arm assembly.
* Got refusal of visa from Irish embassy. Ran after visa consultants
for issues related to visa application.
* Calls with Irish consulate officers for appeal process and causes of refusal.
== Plan ==
* Submit ready patches for dwarf2 untested/unsupported problems.
* Translate dwarf2 tests written in x86 to arm asm.
* Chromebook os update on a faster sd card. (Still pending)
* Add JIRA cards for gdb features missing on arm. (Still pending)
* Prepare documentation for future visa applications.
== Issues ==
* None
== Progress ==
* Investigate conditional compare RTL representation.
- Expand conditional compare to cmp_and/cmp_ior.
- Test is ongoing
* Investigate lp: 1189445. Patch is in testing.
* Identify the root cause for lp: 1189448. FSF4.8 does not have the
buggy code. Linaro 2013.06 and trunk have fixed it.
== Plan ==
* Continue on conditional compare.
== Public Holiday ==
* Monday, 10 June (4 day week)
== Progress ==
* VRP based zero/sign extension
- Pinged the patch.
* Generate a single call to divmod
- Builtin based implementation bootstrapped and passes regression.
- posted patch and initiated discussion
(http://gcc.gnu.org/ml/gcc/2013-06/msg00100.html)
- long long is not handled now
* Better end of loop counter optimisation
- Dropped md patch
- Verified that Bin Cheng's RTL change noop_move_p fixes this.
== Plan ==
* Respond to patch review
* Set-up X86 benchmarking locally for Spec2k
== Progress ==
* Did QEMU testing for the release by running several images on a
few platforms.
* Did the GCC 4.7-2013.06 release.
* Did the GCC 4.8-2013.06 release.
* Did a spin of the GCC 4.7-2013.06 release.
* Updated benchmark parsing scripts, downloaded historical
benchmark data and data from the release testing.
* Updated SQL query and gnuplot scripts to work with new data.
* Produced some benchmark graphs.
* Finally figured out how to spawn remote Cbuildv1 tests and
benchmarks.
== Plan ==
* Focus on performance and regression test graphs.
* Do builds of FSF GCC branches to compare with Linaro branches.
* Continue improving Cbuildv2 as use it to do all these builds and
testing.
- rob -
== Progress ==
* Branched and released binutils, newlib and eglibc.
* Wrote up some release process docs on the wiki.
* Fixes and further investigation of AArch64 ifunc issue.
* Submitted memcpy to upstream gerrit and ran more benchmarks.
* Submitted new fix for gdb frexpl issue.
== Issues ==
* None.
== Plan ==
* Fix AArch64 ifunc issue.
* Fix gdb.thread issue.
* strlen
--
Will Newton
Toolchain Working Group, Linaro
[very short week; two days]
Progress:
* misc
** made qemu-linaro 2013.06 release
** remaining VIRT-4 work handed over to other people for now
** Huawei's AArch64 TCG patches now committed upstream
** working through mach-virt and virtio patches to see what
still needs to be done here and in what order
Plans:
* continue mach-virt/virtio work
* 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 ==
* Pandaboard
- Using GNU ld didn't help the problem, and made compilation time double
to 5hs!
- Reverting to Gold and will keep an eye on it
* Release 3.3 finished
- Tested and released, just waiting the final email
* Linaro+ARM sync meeting
- Setting priorities, requesting approval for some work items
* Phoronix
- Script to run batch mode ready at:
http://people.linaro.org/~rengolin/llvm/scripts/
- Got some results, generally on par, some big differences could be due to
compilation options
- Some tests still run GCC, even with CC being Clang, Clang-only options
(slp vect) cannot be tested
- No way yet to share this data internally, working with IT to find a
solution
* CBuild
- Merged Clang changes, running job again
- Autodetecting ARMv7
* LLVM administrativia
- many patches to review this week
- vectorizer also being enabled by default on -O2 and -Os
- testing vectorizer with -Os on chromebook, found no big differences
== Issues ==
None
== Plan ==
* Phoronix
- Store the base runs somewhere (people.linaro?) and have the script
install them to compare with any run on the board.
- 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
* Pandaboard
- Use GCC 4.8 on linaro-panda-02 and hope to solve the problem
* CBuild
- Finish LLVM+Clang change (merge pending) and try to run some benchmarks
with it
* PerfDB
- Install website locally, try to cook some analysis
### About Linaro binutils
Linaro binutils is a release of the GNU binutils with bug fixes and
enhancements for ARM platforms. GNU binutils is a collection of tools
including the `ld` linker and `as` assembler.
### Linaro binutils 2.23.2 2013.06
The Linaro Toolchain Working Group is pleased to announce the 2013.06
release of Linaro binutils 2.23.2, the first release in the 2.23 series.
This release is based on the latest GNU binutils 2.23 stable branch, but
with additional features and bug fixes.
#### Additional Features
* None
#### Bug Fixes
* Bug fix for ARM support of GNU indirect functions
### Source
#### Release Tarball
* https://releases.linaro.org/13.06/components/toolchain/binutils-linaro
#### Development Tree
* git://git.linaro.org/toolchain/binutils.git
This release was built from the `linaro_binutils-2_23_2-2013_06_release` tag.
### Feedback and Support
Subscribe to the important Linaro mailing lists and join our IRC channels to
stay on top of Linaro development.
* Linaro Toolchain Development [mailing
list](http://lists.linaro.org/mailman/listinfo/linaro-toolchain)
* Linaro Toolchain IRC channel on irc.freenode.net at `#linaro-tcwg`
* Questions? [ask Linaro](http://ask.linaro.org/).
* Interested in commercial support? inquire at [Linaro
support](mailto:support@linaro.org)
--
Will Newton
Toolchain Working Group, Linaro
### About Linaro newlib
Linaro newlib is a release of the newlib C library with bug fixes and
enhancements for ARM platforms. newlib is a small footprint C library
designed for embedded systems.
### Linaro newlib 2.0.0 2013.06
The Linaro Toolchain Working Group is pleased to announce the 2013.06
release of Linaro newlib 2.0.0, the first release in the 2.0.0 series.
This release is based on the latest upstream newlib trunk, but with
additional features and bug fixes.
#### Additional Features
* Faster memcpy implementation for hardware with NEON or VFP support.
#### Bug Fixes
* None
### Source
#### Release Tarball
* https://releases.linaro.org/13.06/components/toolchain/newlib-linaro
#### Development Tree
* git://git.linaro.org/toolchain/newlib.git
This release was built from the `linaro_newlib-2_0_0-2013_06_release` tag.
### Feedback and Support
Subscribe to the important Linaro mailing lists and join our IRC channels to
stay on top of Linaro development.
* Linaro Toolchain Development [mailing
list](http://lists.linaro.org/mailman/listinfo/linaro-toolchain)
* Linaro Toolchain IRC channel on irc.freenode.net at `#linaro-tcwg`
* Questions? [ask Linaro](http://ask.linaro.org/).
* Interested in commercial support? inquire at [Linaro
support](mailto:support@linaro.org)
--
Will Newton
Toolchain Working Group, Linaro
### About Linaro eglibc
Linaro eglibc is a release of the eglibc C library with bug fixes and
enhancements for ARM platforms. eglibc is a variant of the GNU libc
designed to work well on embedded systems.
### Linaro eglibc 2.17 2013.06
The Linaro Toolchain Working Group is pleased to announce the 2013.06
release of Linaro eglibc 2.17, the first release in the 2.17 series.
This release is based on the latest upstream eglibc 2.17 stable branch,
but with additional features and bug fixes.
#### Additional Features
* Faster memcpy implementation for hardware with NEON or VFP support.
#### Bug Fixes
* None
### Source
#### Release Tarball
* https://releases.linaro.org/13.06/components/toolchain/eglibc-linaro
#### Development Tree
* git://git.linaro.org/toolchain/eglibc.git
This release was built from the `linaro_eglibc-2_17-2013_06_release` tag.
### Feedback and Support
Subscribe to the important Linaro mailing lists and join our IRC channels to
stay on top of Linaro development.
* Linaro Toolchain Development [mailing
list](http://lists.linaro.org/mailman/listinfo/linaro-toolchain)
* Linaro Toolchain IRC channel on irc.freenode.net at `#linaro-tcwg`
* Questions? [ask Linaro](http://ask.linaro.org/).
* Interested in commercial support? inquire at [Linaro
support](mailto:support@linaro.org)
--
Will Newton
Toolchain Working Group, Linaro
The Linaro Toolchain Working Group is pleased to announce the release of
Linaro QEMU 2013.06.
Linaro QEMU 2013.06 is the latest release of qemu-linaro. Based off
upstream (trunk) QEMU, it includes a number of ARM-focused bug fixes
and enhancements.
This release has been updated to be based on upstream's recent 1.5.0
release. Interesting ARM related upstream changes include fixes to
the VersatilePB and Realview model PCI controller, improved performance
of emulation of ARM targets, and working VM save/load for vexpress-a15
and vexpress-a9 board models.
The source tarball is available at:
https://launchpad.net/qemu-linaro/+milestone/2013.06
More information on Linaro QEMU is available at:
https://launchpad.net/qemu-linaro
-- PMM
== Progress ==
* Merges for linaro-4.8-2013.06 and linaro-4.7-2013.06
- Spent most of my time on this activity, with Yvan
- A few cbuild issues, local disk full, and other local disk crash
- Investigating why the cross-validations lack libpthread and libdl
(required since libsanitizer backport). The libs are present, but not
found by the compiler.
* Registered for Connect/Dublin
== Next ==
* Complete merges quickly, to enable release this week.
* Disable-peeling: resume work
* Better end of loop counter optim: discuss with Kugan
* libsanitizer/aarch64: resume work
* Neon intrinsics/vzup/veor: resume work
* Book hotel/flight for Connect/Dublin
== Issues ==
* None.
== Progress ==
* Releases merge reviews:
- Most of the week spent on this activity
- Lot of reviews and cbuild issues
- some reviews still on-going
* Jira cards:
- Closed card #108 on Tiny memory model support.
- Created Card #167 for TLS support in the Tiny memory model.
* LRA on ARM and AArch64:
- Raise the issue to LRA maintainer (Vladimir Makarov)
- will iterate with him in the coming weeks.
* Launchpad bug #1187247
- started to look at it.
== Plan ==
* Finishing reviews
* Bug #1187247
* LRA
== 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.
