- linaro-toolchain - lists.linaro.org

[ANNOUNCE] Linaro Toolchain Binaries 2013.06 released

by Bernhard Rosenkränzer

The Linaro Toolchain and Platform Working Groups are pleased to announce the 2013.06 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.06 * Linaro Newlib 2.0 2013.06 * Linaro Binutils 2.23 2013.06 * Linaro Eglibc 2.17-2013.06 (Aarch64 only) * 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: * Linaro versions of Binutils, Newlib and Eglibc are included 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. Note: This will likely be the last release built with support for (e)glibc 2.15 on armv7. With future releases, you will have to either use a newer (e)glibc on the target system, or link statically.

13 years, 1 month

2
1
0 0

Re: [Buildroot] Bizarre behavior of armeb toolchain

by Will Newton

On Thu, Jun 20, 2013 at 2:41 PM, Thomas Petazzoni <thomas.petazzoni(a)free-electrons.com> wrote: > Hello, > > I'm facing a bizarre problem with an armeb toolchain built by > Buildroot. I'm also posting this to the crossgcc@ list since there are > some gcc/binutils experts out there. > > First, a little bit of background. ARM Big Endian comes into two > variants: > > * BE32, which was used up to ARMv5, where both the instructions and > the data are Big Endian. > > * BE8, which is used since ARMv6, where the instructions remain > little-endian and only the data are big-endian. > > See > http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0338g/ch06s0… > for some details about this. > > So, I've built an ARMv7 Cortex-A8 toolchain, with the armeb > architecture selected. The CROSS-gcc -v shows that it was configured as > follows: > > --target=armeb-buildroot-linux-uclibcgnueabi > --with-abi=aapcs-linux > --with-arch=armv7-a > --with-tune=cortex-a8 > > Then, I wrote a simple program that contains some data and > instructions, built it under several conditions, and observed with > hexdump whether the data and code was little-endian or big-endian. > > And the results are somewhat surprising: when I explicitly pass > -mbig-endian, I get the proper behavior (BE8 code with code in little > endian and data in big endian), but when I don't pass any flags to the > compiler, I get an incorrect behavior: both the code and data are big > endian, as if the BE8 wasn't used (and readelf confirms that it wasn't > used). See below the detailed results. > > Note that the compiler is supposed to automatically use BE8 on > ARMv6/ARMv7 and BE32 on ARMv5 and earlier cores. > > The data is DEADBEEF, and the instruction is E52DB004. > > Flags used Observed data Observed code Comment > ======================= =============== =============== ========================================= > > -mlittle-endian EFBEADDE 04B02DE5 Code and data in LE -> OK > -mbig-endian DEADBEEF 04B02DE5 Code LE, data BE, binary marked BE8 -> OK > no flags DEADBEEF E52DB004 Data BE (ok!), code BE (*NOT* ok) -> NOK > -march=armv5t -mbig-endian DEADBEEF E52DB004 Code and data in BE, on ARMv5 -> OK > -march=armv5t DEADBEEF E52DB004 Code and data in BE, on ARMv5 -> OK > > As can be seen in this table: > > (*) On ARMv5, regardless of whether -mbig-endian is passed or not, the > code produced is correct (both code and data are big endian, which is > correct for ARMv5 where the big endian mode is BE32) > > (*) On ARMv7 however, the code is different whether -mbig-endian is > passed or not, even though an "armeb-linux" compiler is supposed to > generate big endian code by default. When no flags is passed, both the > data *and* code are big-endian (so it's BE32 like on ARMv5), but > passing -mbig-endian makes the thing behave properly (code is > little-endian, data is big-endian). > > I'm using binutils 2.23.2 and gcc 4.7.3. > > Any ideas? Hi Thomas, I added linaro-toolchain to CC as there may be someone there who knows the answer.

13 years, 1 month

1
0
0 0

RE: Semi-hosting on v8 Foundation Model using gnu tools

by rorycollins＠hushmail.com

I got an app to compile fine for v8 FM with gcc, but I notice that seg-faults hang the simulator. Using raise() properly exits FM, but I can't seem to trap the seg-fault with signal() or do anything intelligent to know about the seg-fault. Normal execution works well. int main(int argc, char *argv[]) { * (unsigned int *) (0) = 0; // seg-fault hangs FM return(0); } thanks, Rory -----Original Message----- From: linaro-toolchain-boun...(a)lists.linaro.org [mailto:linaro-toolchain-boun...@lists.linaro.org] On Behalf Of Matthew Gretton-Dann Sent: Sunday, May 19, 2013 2:47 PM To: Padgett Don-B43265 Cc: linaro-toolchain(a)lists.linaro.org Subject: Re: Semi-hosting on v8 Foundation Model using gnu tools Don, On 17/05/13 20:57, Padgett Don-B43265 wrote: > The v8 Foundation Model User Guide has a bare metal hello world example > that uses semi-hosting. The Makefile uses ARM tools, however. Is there > equivalent support for this example using a bare metal version of the > gnu tools, such as > gcc-linaro-aarch64-none-elf-4.8-2013.04-20130422_linux.tar.xz? I took > a look, but didn't see a way to do this. It is possible but not necessarily easy. Using the binary tools you've downloaded you will want to do something like the following: aarch64-none-elf-gcc -specs=elf-aem-ve.specs ... The -specs option has to be on all your invocations of GCC and G++. You should also invoke the linker through GCC with this option. Then you need to invoke the model, given an image called foo.axf: Foundation_v8 --image foo.axf --semi-host="foo.axf OPT1 OPT2" --quiet Note that the first option to --semi-host is the name of the image again. Thanks, Matt

13 years, 1 month

1
0
0 0

Re: gcc 4.8-2013.06 reports incorrect version number

by Mans Rullgard

You'll have better luck sending bug reports to the linaro-toolchain mailing list. On 18 June 2013 11:50, Bernhard Rosenkränzer <bernhard.rosenkranzer(a)linaro.org> wrote: > Hi, > the 4.8-2013.06 tarball built without version overrides reports itself as: > 4.8-2013.06-0~dev > Looks like the release flag isn't set in the tarball. > > ttyl > bero -- Mans Rullgard / mru

13 years, 1 month

1
0
0 0

[ACTIVITY] 10-14 June 2013

by Christophe Lyon

== Progress == * Merges for linaro-4.8-2013.06: - investigated why the cross-validation lack libpthread and libdl. - fixed cbuild to make these libs available in the same dir as ld-linux.so - not sure why it wasn't necessary several weeks ago when I first spawn libsanitizer tests: we changed the prebuilt tarball since then, but the libs are still at the same place; the binutils version changed though. * Re-spawned a merge request for libsanitizer, using the updated cbuild (libpthread/libdl support, qemu flags updated) and the updated gcc-4.8 (with my patch to cope with qemu's output of /proc/self/maps) * Merges for linaro-4.8-2013.07: updated list * Aarch64 frame growing downward: started. * Disable-peeling: restarting looking at vectorizer. == Next == * Merges for linaro-4.[78]-2013.07: update list * disable peeling: see how to make the vectorizer less aggressive * Aarch64 frame growing downward. * Neon intrinsics/vuzip/veor: resume work * Book hotel/flight for Connect

13 years, 1 month

1
0
0 0

[ACTIVITY] Week 24

by Yvan Roux

== Issues == * None. == Progress == * Releases merge reviews: - Finished reviews for releases. * Launchpad bug #1187247: - Closed as invalid since the issue was on an attempt to access at an invalid address. * Cbuild Babysitting: - Fixed 4.8 repository update on toolchain64. - Recreate ancestors tarballs and re-spawned jobs - Re-started Calxedas... * LRA on ARM and AArch64: - Resumed the task. - Investigation of AArch64 failure on-going. == Plan == * Mainly LRA

13 years, 1 month

1
0
0 0

[ACTIVITY] 10-14 June 2013

by Venkataramanan Kumar

== Progress == * libssp support for AArch64 Libssp support needed AArch64 frame to grow downward. But it is currently defined as growing upward. This work is currently in hold. Needed frame layout changes before restarting. Waiting for feedback from Matt. * AAarch64 testing Drilling down Boot strap failure with GCC 4.9 trunk on open embedded image with V8 model. Fails at time xg++ is linking. Not much progress. Set up Cross build and test in V8 model for GCC testsuites. Also looking at increasing timeout for individual tests. * AArch64 LTO and PGO support. Started on understanding PGO and LTO runs with AArch64. == Plan == * Continue bootstrap testing and push patches to GCC * Continue LTO and PGO runs for AArch64

13 years, 1 month

1
0
0 0

[ACTIVITY] 10 - 14 June 2013

by Omair Javaid

== 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.

13 years, 1 month

1
0
0 0

[ACTIVITY] Week 24

by Zhenqiang Chen

== 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.

13 years, 1 month

1
0
0 0

[ACTIVITY] 11-14 June 2013

by Kugan

== 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

13 years, 1 month

1
0
0 0

[ACTIVITY] week 24

by Rob Savoye

== 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 -

13 years, 2 months

1
0
0 0

[ACTIVITY] Week 24

by Will Newton

== 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

13 years, 2 months

1
0
0 0

[ACTIVITY] report week 23

by Peter Maydell

[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

13 years, 2 months

1
0
0 0

[ACTIVITY] Week 24

by Renato Golin

== 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

13 years, 2 months

1
0
0 0

[ANNOUNCE] Linaro GCC 4.8 and 4.7 2013.06 released

by Rob Savoye

The Linaro Toolchain Working Group is pleased to announce the 2013.05 release of Linaro GCC 4.8 and Linaro GCC 4.7. Linaro GCC 4.8 2013.05 is the third release in the 4.8 series. Based off the latest GCC 4.8.0+svn200019 release, it includes performance improvements and bug fixes. Linaro GCC 4.7 2013.06 is the 15th release in the 4.7 series. Based off the latest GCC 4.7.3+bzr115076 release, this is the first release after entering maintenance. The source tarball is available from: https://launchpad.net/gcc-linaro/+milestone/4.7-2013.06 https://launchpad.net/gcc-linaro/+milestone/4.8-2013.06 Downloads are available from the Linaro GCC page on Launchpad: https://launchpad.net/gcc-linaro Mailing list: http://lists.linaro.org/mailman/listinfo/linaro-toolchain Bugs: https://bugs.launchpad.net/gcc-linaro/ Questions? https://ask.linaro.org/ Interested in commercial support? Inquire at support(a)linaro.org

13 years, 2 months

1
0
0 0

[ANNOUNCE] Linaro binutils 2.23.2 2013.06 released

by Will Newton

### 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

13 years, 2 months

1
0
0 0

[ANNOUNCE] Linaro newlib 2.0.0 2013.06 released

by Will Newton

### 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

13 years, 2 months

1
0
0 0

[ANNOUNCE] Linaro eglibc 2.17 2013.06 released

by Will Newton

### 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

13 years, 2 months

1
0
0 0

[ANNOUNCE] Linaro QEMU 2013.06 released

by Peter Maydell

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

13 years, 2 months

1
0
0 0

[ACTIVITY] 3-7 June 2013

by Christophe Lyon

== 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

13 years, 2 months

1
0
0 0

[ACTIVITY] Week 23

by Yvan Roux

== 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

13 years, 2 months

1
0
0 0

[ACTIVITY] 03-07 June 2013

by Venkataramanan Kumar

== 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.

13 years, 2 months

1
0
0 0

[ACTIVITY] week 23

by Rob Savoye

== 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 -

13 years, 2 months

1
0
0 0

[ACTIVITY] 3 - 7 June 2013

by Omair Javaid

== 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.

13 years, 2 months

1
0
0 0

[ACTIVITY] 2 - 7 June

by Kugan

== 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.

13 years, 2 months

1
0
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain