- linaro-toolchain - lists.linaro.org

[Weekly] 24-28 NOV 2014

by Michael Collison

== This week == * GCC Modularization Project (5/10) - Flattening header files - tree-core.h - Building revealed required flattening other include files: c-common.h and tree.h - c-common.h and tree.h - Flattening is in progress - cfgloop.h - Reviewed, bootstraped and tested patch from Prathamesh * Misc (1/10) - Conference calls * Thanksgiving Holiday, November 27-28th (4/10) == Next week == - Complete tree-core.h and associated header file flattening - submit tree-core.h flattening patch - Submit Prathamesh patches for cfgloop.h

11 years

1
0
0 0

[ACTIVITY] 24-28 November 2014

by Prathamesh Kulkarni

== This week == * GCC Modularization Project - created initial patch for flattening cfgloop.h. - created initial patch for flattening df.h. == Next Week == - Finalizing patches for cfgloop.h and df.h. - Continue working on flattening header files.

11 years

1
0
0 0

[ACTIVITY] 24-28 November 2014

by Kugan

== Progress == * Zero/sign extension elimination with widening types (1/10) - Addressing comments from the review * BUG #398 #412 (5/10) - built kernel revision with provided config and toolchain binary release to reproduce gcc segafult. Couldn’t reproduce it. Since there is no more details to reproduce, closed it as cant reproduce. - Spec2k gcc optimization issue was reproduced and reduced test-case was created. - dumps shows that this issue could be related to splitting constants for early during expand might be the root cause. * Holiday (4/10) == Plan == * Continue with Zero/sign extension. * BUG #412 == Planned Leave == * 11/12/2014 to 24/12/2014 - 10 days

11 years

1
0
0 0

[ACTIVITY] 24-28 November 2014

by Christophe Lyon

== Progress == * GCC trunk/4.9 cross-validation (1/10) - monitoring - tracking cause of spurious "interrupted system call" - testing small changes in harness * AArch64 sanitizers (2/10) - resumed discussion with Maxim/Arnd, the situation is clearer now - started looking at running asan tests in llvm environment (Thanks Renato) * Linaro GCC releases (2/10) - 2014.12 backports reviews - improved scripts to help speed up reviews * Neon intrinsics tests (2/10) - continuing to convert the existing testsuite to dejagnu - checking ARM's aarch64_be patches * Misc (3/10) - calls, meetings, ... == Next == * Neon intrinsics * AArch64 sanitizers * cbuild2 (improve backport-test and tcwgweb)

11 years

1
0
0 0

[ACTIVITY] Week 48

by Renato Golin

== Progress == * 2 days sick * Lab move (2/6) * Buildbots (TCWG-76 2/6) - Created a buildmaster at Linaro to help local development - Put a dragonboard as a slave, which lasted 2 days up * Background (2/6) - Code review, meetings, discussions, etc. == Plan == * I have no idea

11 years

1
0
0 0

[ACTIVITY] 24 - 28 November 2014

by Will Newton

== Progress == * Building an ILP32 toolchain for AArch64 (3/10, TCWG-559) - More work on tidying patches - Trying to get a test environment for ILP32 * LLD for ARM and AArch64 (5/10) - Submit more reloc cleanups for LLVM - Patch review - Reading code * glibc patch review (1/10, CARD-341) * Email, meetings, etc. (1/10) == Issues == * OE on Junos no good for building toolchains * Ubuntu on Junos still seems vaporware * Running out of disk space on development machine (bought an external HD) == Plan == * More work on LLD * Try QEMU for ILP32 work -- Will Newton Toolchain Working Group, Linaro

11 years

1
0
0 0

[ACTIVITY] 24th - 28th November

by Bernie Ogden

ABE benchmarking - TCWG-360 [4/10] * Implemented most of a solution to the 'must be in same network' restriction libm exercising - TCWG-558 [4/10] * lulesh generates needless calls to pow on AArch64 (as opposed to 'pow is slow') ** Working on a reduced test case * Ran a chunk of benchfft, left a process searching the perf reports for libm calls * More chroot/glibc fiddling * Decided Graph500 was unlikely to be interesting Misc - [2/10] =Plan= On holiday Monday - Wednesday More lulesh, benchfft results Think about where to go next with libm exercising Complete 'same network' workaround, test benchmark repeatability Port benchmarking scripts to ABE repo Get storage/automation started, if Rob has time

11 years

1
0
0 0

building eglibc for arm-linux-gnueabihf tools with multilib support

by Mallikarjun.Gouda＠freescale.com

Hi All, Currently linaro toolchain for arm-linux-gnueabihf built with crosstool-ng scripts uses prebuilt sysroot. I am trying to build eglibc on my own without using prebuilt sysroot. I am not able to exactly create same layout in the library layout. Linaro build layout looks: gcc-linaro-arm-linux-gnueabihf-4.8-2014.01_linux\arm-linux-gnueabihf\libc\usr\lib --> arm-linux-gnueabi arm-linux-gnueabihf one for soft float and other for hard float fp. Can anybody please tell how we tell build system to create directories like above while building eglibc? I used following commands to build eglibc: ../src_eglibc/configure --disable-profile --without-gd --without-cvs --prefix=/usr libc_cv_forced_unwind=yes libc_cv_c_cleanup=yes --with-headers=<some_dir>/arm-linux-gnueabihf/libc/usr/include --host=arm-linux-gnueabihf Make all make install install_root= <some_dir>/arm-linux-gnueabihf/libc/ Thank you very much for your help. //Mallikarjuna

11 years

2
2
0 0

Fw: strange behavior in GCC for use of uninitialized variables

by Pinski, Andrew

Forwarding this message to the linaro toolchain list instead. I am not the person who should be supporting the Linaro ODP project with GCC questiosn; the toolchain team inside Linaro should be instead. Thanks, Andrew Pinski ________________________________________ From: Ola Liljedahl <ola.liljedahl(a)linaro.org> Sent: Monday, November 24, 2014 2:31 PM To: lng-odp(a)lists.linaro.org; Pinski, Andrew Subject: strange behavior in GCC for use of uninitialized variables Consider the following code fragment (from real life): #include <stdint.h> typedef volatile uint32_t odp_atomic_u32_t; static inline uint32_t odp_atomic_fetch_inc_u32(odp_atomic_u32_t *ptr) { return __sync_fetch_and_add(ptr, 1); } static inline void odp_spin(void) { #ifdef __SSE2__ __asm__ __volatile__ ("pause"); #else __asm__ __volatile__ ("rep; nop"); #endif } typedef struct { int count; odp_atomic_u32_t bar; } odp_barrier_t; void odp_barrier_wait(odp_barrier_t *barrier) { uint32_t count; int wasless; // wasless = barrier->bar < barrier->count; <<<lost on git add -p __atomic_thread_fence(__ATOMIC_SEQ_CST); count = odp_atomic_fetch_inc_u32(&barrier->bar); if (count == 2*barrier->count-1) { barrier->bar = 0; } else { while ((barrier->bar < barrier->count) == wasless) odp_spin(); } __atomic_thread_fence(__ATOMIC_SEQ_CST); } While fixing and cleaning up this code, the indicated line that initializes 'wasless' was dropped (because it reappears in a later patch in the patch set after the odp_atomic_fetch_inc call). To my surprise, GCC did not complain when compiling this file (using -O2 -Wall). But it does complain when compiling with -O0 -Wall. With some investigation, it seems like GCC understands that if a statement does not have any side effects so it can optimize away everything, including the usage of the uninitialized variable and thus also the corresponding warning. olli@macmini:~/hacking/gcc-wunit$ gcc -O2 -Wall -c odp_barrier.c olli@macmini:~/hacking/gcc-wunit$ gcc -O0 -Wall -c odp_barrier.c odp_barrier.c: In function ‘odp_barrier_wait’: odp_barrier.c:42:9: warning: ‘wasless’ may be used uninitialized in this function [-Wmaybe-uninitialized] while ((barrier->bar < barrier->count) == wasless) ^ However the proper code seems to be generated in both cases (there is a "pause" instruction inlined or a call to odp_spin). So odp_spin() is not without side effects and is not optimized away. This contradicts my hypothesis. Consider this minimalistic example: olli@macmini:~/hacking/gcc-wunit$ cat wunit.c #include <stdlib.h> void test(void) { int wasless; int wasmore; if (wasless) (void)0; if (wasmore) abort(); } olli@macmini:~/hacking/gcc-wunit$ gcc -O0 -Wall -c wunit.c wunit.c: In function ‘test’: wunit.c:9:5: warning: ‘wasmore’ is used uninitialized in this function [-Wuninitialized] if (wasmore) abort(); ^ olli@macmini:~/hacking/gcc-wunit$ gcc -O2 -Wall -c wunit.c wunit.c: In function ‘test’: wunit.c:9:5: warning: ‘wasmore’ is used uninitialized in this function [-Wuninitialized] if (wasmore) abort(); ^ Here GCC warns when used with both -O0 and -O2 but only for the usage where there is a side effect. The use of 'wasless' that does not lead to any side-effects is ignored (and possibly rightly so, I can imagine this is undefined behavior, fortunately I did not attempt to run this program or my computer could have melted). It is a bit worrying to me that instances of use of initialized variables is sometimes missed by GCC. Both because of lack of diagnostics for what is most likely a bug but also because I don't understand why GCC does this and the implications of that (at least it is a known unknown now). -- Ola

11 years

4
4
0 0

[ACTIVITY] 17th - 21st November

by Bernie Ogden

cbuild2/ABE benchmarking - TCWG-360 [1/10] * Attempted to use LAVA for benchmarks ** Fell over on lack of TCWG machines in same network libm exercising - TCWG-558 [6/10] * Much fiddling with chroots * Some fiddling with benchfft * Little actual progress Meetings/mail/etc - [3/10] =Plan= libm exercising * Run benchfft in chroots * Investigate Graph500 * Validate existing results with consistent methodology ** Hopefully this is reaching the point of handle-turning ABE benchmarking * Port 'cbuild2' benchmarking to ABE repository * Test ABE benchmarking in TCWG lab (and LAVA?) * Test repeatability (assuming the above go well) * Get storage/automation started, if Rob has time Holiday *next* week (Tuesday and Wednesday, perhaps Monday as well)

11 years

1
0
0 0

[ACTIVITY] 17 - 21 November 2014

by Will Newton

== Progress == * Building an ILP32 toolchain for AArch64 (4/10, TCWG-559) - Applied a few simple ILP32 patches to glibc - Rebasing and reworking existing ILP32 glibc patches * LLD for ARM and AArch64 (5/10) - Submit first set of reloc cleanups for LLVM * Email, meetings, etc. (1/10) == Issues == * None == Plan == * Submit more ILP32 patches for glibc * Further LLVM/LLD changes -- Will Newton Toolchain Working Group, Linaro

11 years

1
0
0 0

[ANNOUNCE] Linaro Toolchain Binaries 2013.07 released

by Zhenqiang Chen

The Linaro Toolchain and Platform Working Groups are pleased to announce the 2013.07 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.07-1 * Linaro Newlib 2.0 2013.06 * Linaro Binutils 2.23 2013.06 * Linaro Eglibc 2.17-2013.07-2 * 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: * The sysroot is based on Linaro versions of Eglibc. About details of Linaro Eglibc, please refer https://releases.linaro.org/13.07/components/toolchain/eglibc-linaro. 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.07 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. Know issues: * Some version information in README are incorrect. * gdb can not backtrace into libc. Notes: * To use all of the features of Linaro eglibc, the sysroot in 32-bit toolchain release is updated to Linaro eglibc, which is 2.17. If you get runtime errors about libc version, please get the sysroot from the release tarball (gcc-linaro-arm-linux-gnueabihf-4.8-2013.07-1_linux/arm-linux-gnueabihf/libc/) or download from launchpad https://launchpad.net/linaro-toolchain-binaries/support/01/+download/linaro… If you do not want to use Linaro sysroot, you'd add option to gcc to find your sysroot: --sysroot=<directory> * To run 32-bit application built from arm-linux-gnueabihf toolchain in aarch64 system, you'd copy sysroot and runtime from release package to your root of aarch64 system. i,e. scp -r gcc-linaro-arm-linux-gnueabihf-4.8-2013.07-1_linux/arm-linux-gnueabihf/libc/* AARCH64-SYSTEM:/ scp -r gcc-linaro-arm-linux-gnueabihf-4.8-2013.07-1_runtime/* AARCH64-SYSTEM:/

11 years

2
1
0 0

[ACTIVITY] Week 47

by Yvan Roux

== Issues == * none. == Progress == * GCC 4.9 2014.12 (2/10) - Back on Backports. - Around 30 revisions backported are under review. * AArch64 libunwind/ptrace (6/10) - Remote unwinding is not working because of a wrong ptrace invocation. - Implement registers access with PTRACE_GETREGSET * Misc: (2/10) - GCC git mirror migration. - Various meetings. == Plan == * Backports * Libunwind

11 years

1
0
0 0

[Weekly] 17-21 NOV 2014

by Michael Collison

== This week == * GCC Modularization Project (7/10) - Flattening header files - Submitted gimple-streamer.h, tree-streamer.h, lto-streamer.h patches to gcc-patches list - tree-core.h - Several rounds of changes based on review and bootstraps - final fifty target bootstrap in progress - df.h - Initial round of changes - cfgloop.h - Initial patch created by Parthamesh * Bug fixing (2/10) - Investigation of bug 539 - .LTHUNK symbols are surviving * Misc (1/10) - Conference calls - Worked with Prathamesh to bootstrap him on GCC modularization project == Next week == - Submit tree-core.h patches - Complete df.h pathces - Review Prathamesh's patches to cfgloop.h - Thanksgiving holiday, November 27-28

11 years

1
0
0 0

[ACTIVITY] 17 - 21 November 2014

by Kugan

== Progress == * Zero/sign extension elimination with widening types (2/10) - Addressing comments from the review * Improve block memory operations by GCC (TCWG-142 - 3/10) -Looked at ARM vs AArch64 * BUG #880 (3/10) - Analysed tree dumps. - Updated bug report with the findings. * MISC (2/10) - Looked at git and stg documents == Plan == * Continue with Zero/sign extension. == Planned Leave == * 27/11/2014 to 28/11/2014 - 2 days * 11/12/2014 to 24/12/2014 - 10 days

11 years

1
0
0 0

[ACTIVITY] Week 47

by Renato Golin

== Progress == Lab move (for the last 11 days non-stop) == Plan == Sleep

11 years

1
0
0 0

[ACTIVITY] 10 - 14 November 2014

by Omair Javaid

== Progress == Environment setup, installations, board setup etc [4/10] -- Prepared a local dev machine to work with in absence of lab. -- Prepare panda board for gdb on android testing. -- Figure out SSH failure issues with gdb testsuite runs. -- Try out foundation model for android testing. -- Getting to know CBuildv2 tried to set it up locally. On travel to submit Hong Kong visa application [5/10] Miscellaneous [1/10] -- Meetings, Emails etc == Plan == Try android boot with foundation model some more and hope that it works. Resume AArch64 work with lab availability. Review and update GDB related cards.

11 years

1
0
0 0

[Activity] Week 46

by Charles Baylis

== Progress == bug #403/418 [5/10] . submitted partial patch to list for core fix for Aarch64 . needs reworking of expansion for a bunch of builtins + corresponding patterns . discussion/review of related upstream patches bug #868 - brief investigation [1/10] Misc [4/10] == Plan == On holiday on Friday and following Monday morning

11 years

1
0
0 0

[ACTIVITY] Week 46

by Yvan Roux

1 day off (2/10) == Issues == * none. == Progress == * GCC 4.9 and 4.8 2014.11 (6/10) - Backported ILP32 related commits in 4.9 - Validate and committed Linaro release macros in Linaro branches. - Released 4.9 and 4.8 2014.11 * Lab move (1/10) - Tested new validation infrastructure. * Misc: (1/10) - Finished libunwind task - Various meetings. == Plan == * Back on backports

11 years

1
0
0 0

[ACTIVITY] 10th - 14th November

by Bernie Ogden

cbuild2 benchmarking - TCWG-360 [5/10] * Fixed some bugs and did some general tidying up * Pulled SPEC2000 into my framework * Did some test runs on local machines, looks promising libm exercising - TCWG-558 [3/10] * Much fiddling with one benchmark (MCB) * Experimented, thought about methodology Meetings/mail/etc - [2/10] =Plan= cbuild2 benchmarking * Tweak eembc - it worked before, but spec forced me to change the scripts a little * Test in LAVA/new TCWG infrastructure when available * Test repeatability (depends on above) * Possibly have another go at building tools on AArch64 libm exerising * Work through the most interesting benchmarks with a fixed method * Hopefully reach the end and do some analysis

11 years

1
0
0 0

[ACTIVITY] 10 - 14 November 2014

by Venkataramanan Kumar

= Progress == * TSAN support for Aarch64 (4/10) * Fix Linaro Bug 863,869 - reproduced them. Working on fixing 863 (1/10) * Misc [3/10] Emails, linaro and AMD status meetings. 1-1 with inline mangers (Mev, Ryan). 1-1 with christophe. * 11/11/2014 Leave (2/10) The task on "Debug and understand the inline differences trunk vs linaro compiler for core mark at -O3 with LTO + PGO" is on hold now. == Plan == * TSAN support for Aarch64. * Fix Linaro Bug 863 * AMD internal event on 17/11/2014.

11 years

1
0
0 0

[Weekly] 10-14 NOV 2014

by Michael Collison

== This week == * GCC Modularization Project (4/10) - Flattening header files - gimple-streamer.h, tree-streamer.h, lto-streamer.h - Additional updates based on review: - Additional fixes based on boostrapping in contrib/config-list.mk - Boostrapped changes on all targets in contrib/config-list.mk - New changes being reviewed - Preparing patch - tree-core.h - Completed flattening - Boostrapped changes on all targets in contrib/config-list.mk * Vacation (6/10) == Next week == - Submit gimple-streamer.h, tree-streamer.h, lot-streamer.h patches - Submit tree-core.h patches - Continue flattening include files

11 years

1
0
0 0

[ACTIVITY] 10 - 14 November 2014

by Kugan

== Progress == * Zero/sign extension elimination with widening types (5/10) - Addressing comments from the review * Improve block memory operations by GCC (TCWG-142 - 5/10) - Looked at gcc/glibc implementations - Experimented with x86_64 vs ARM and found different implementation decisions - Discussed work items == Plan == * Continue with improve block memory operations by GCC. * Continue with Zero/sign extension.

11 years

1
0
0 0

[ACTIVITY] 10 - 14 November 2014

by Will Newton

== Progress == * Building an ILP32 toolchain for AArch64 (5/10, TCWG-559) * Investigate ARM port of lld (3/10) * Email, meetings, etc. (2/10) == Issues == * None == Plan == * Further work on ILP32 toolchain * LLD -- Will Newton Toolchain Working Group, Linaro

11 years, 1 month

1
0
0 0

[ACTIVITY] Week 46

by Renato Golin

== Progress == Lab move == Plan == Lab move

11 years, 1 month

1
0
0 0

[ACTIVITY] 10-14 November 2014

by Christophe Lyon

1 day off (2/10) == Progress == * Linaro GCC 4.8 - updated branch merge, to include the latest errata-related backport - added Michael's backport for bug #534. * GCC trunk/4.9 cross-validation (2/10) - updated vbic/vorn tests patch - trying to track down cause of spurious 'interrupted system call' errors in the ST Compute Farm * AArch64 sanitizer (1/10) - After discussing with Arnd, the kernel patch causing trouble to libsanitizer should also be backported to stable kernel branches. This makes a compiler test based on kernel version impracticable. - Shared this feedback with sanitizer maintainers, got no feedback. - libsanitizer maintainers have updated GCC's snapshot with a more recent version: - GCC trunk now requires updated kernel headers for aarch64 - reported regressions when the compiler generates Thumb code (incomplete backtrace) * Neon intrinsics tests (2/10) - submitted a series of 9 new tests. - looking at vldX bugs on aarch64_be, along with ARM's incomplete patches. * cbuild2 - no progress * Misc (3/10) - calls, meetings, support == Next == * AArch64 sanitizers * Neon intrinsics * cbuild2 (improve backport-test and tcwgweb)

11 years, 1 month

1
0
0 0

[ANNOUNCE] Linaro GCC 4.9 and 4.8 2014.11 released

by Yvan Roux

The Linaro Toolchain Working Group (TCWG) is pleased to announce the 2014.11 stable release of both Linaro GCC 4.9 and Linaro GCC 4.8 source packages. With the imminent release of ARMv8 hardware and the recent release of the GCC 4.9 compiler the Linaro TCWG will be focusing on stabilization and performance of the compiler as the FSF GCC compiler. The Linaro TCWG provides stable[1] quarterly releases and monthly engineering[2] releases. Linaro GCC 4.9 2014.11 is the eighth Linaro GCC source package release and second stable one in the 4.9 series. It is based on FSF GCC4.9.3-pre+svn216979 and includes performance improvements and bug fixes. Interesting changes in this GCC source package release include: * Updates to GCC 4.9.3-pre+svn216979 * Backport of [AArch64] Fix ILP32 ld.so * Add new Linaro release macros : __LINARO_RELEASE__ and __LINARO_SPIN__ Linaro GCC 4.8 2014.11 is the fifteenth release in the 4.8 series and second one since entering maintenance. Based off the latest GCC 4.8.4-pre+svn217270 release, it includes performance improvements and bug fixes. Interesting changes in this GCC source package release include: * Linaro bugzilla PR fixed : #307, #534 * Updates to GCC 4.8.4-pre+svn217270 * Add new Linaro release macros : __LINARO_RELEASE__ and __LINARO_SPIN__ 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@ * Bug reports should be filed in bugzilla against GCC product: http://bugs.linaro.org/enter_bug.cgi?product=GCC * Questions? "ask Linaro": http://ask.linaro.org/. * Interested in commercial support? inquire at "Linaro support":mailto: support(a)linaro.org [1] Stable source package releases are defined as releases where the full Linaro Toolchain validation plan is executed. [2] Engineering source package releases are defined as releases where the compiler is only put through unit-testing and full validation is not performed.

11 years, 1 month

1
0
0 0

[Question] Should gdb client query FP registers even if gdb server does not report having org.gnu.gdb.aarch64.fpu feature?

by Qu, Strong

Hello, We have implemented gdb server in one of our project and we are using Linaro aarch64-none-elf-gdb.exe as gdb client. Our gdb server will response to packet 'qXfer:features:read:target.xml:0,fff' with a xml file which only claims feature 'org.gnu.gdb.aarch64.core'. However, when I issue 'info reg' command with the gdb client, it actually sends out a packet '$p42#d6', which is trying to read fpsr if I understand correctly. Is this an expected behavior or not? I just want to figure out whether our gdb server send some bad info to the gdb client and made the client thinks FP registers are valid. I hope I made my question clear and I'm really appreciate if anybody can help us on this again. Thanks, Strong

11 years, 1 month

3
6
0 0

Separate out code used by a pager in OP-TEE

by Jens Wiklander

Hi toolchain champions, [please keep me in cc as I'm not subscribed to linaro-toolchain(a)lists.linaro.org] In OP-TEE we are going to activate a pager which is an integrated part of the statically linked secure OS binary (compiled for ARMv7/Aarch32 now, but at some point also Aarch64). The pager in OP-TEE allows use of more memory than the amount of available physical memory. This makes it possible to for instance have an OP-TEE binary that requires more memory than the amount of available memory. What the pager does is to map a physical page at the virtual address where the memory is needed and populate it which what is expected on demand. The pager also unmaps physical pages that hasn't been used in a while to be able to recycle it. The code used by the pager to map and populate a page must always be mapped since we would otherwise get a deadlock. The problem is that the pager is also part of OP-TEE so we need to partition the binary in a way that all code needed to handle a page fault is in one area in the binary and always mapped. Annotating functions and such as it's done in the Linux kernel with __init will not scale here since the pager will need routines from "third-party" libraries. We can make small changes to the libraries but identifying and annotating everything needed by the pager is too much. We would also run into troubles with strings. I have a couple ideas below that I need help exploring. What if we do an incremental linking of the entire TEE Core with garbage collect only keeping the entry functions of the pager? Then we would get an object file with everything the pager depends on included but not much more. It would be easy to put this single object file in a separate part of the OP-TEE binary. The procedure would be something like: Compile everything with -ffunction-sections -fdata-sections ld -i --gc-sections -u pager_entry -o pager_code.o $(objs) $(link-ldadd) $(libgcc) ld $(link-ldflags) pager_code.o $(objs) $(link-ldadd) $(libgcc) But the problem comes with linking in the rest of the code in the last step, we would get lots of multiple defined symbols. We could create a libtee_core.a file where we put all the $(objs) files and the linker would only use the needed object files. But we would still have some multiple defined symbols left since each .o file contains more than just one section. Any ideas how to solve this? We could perhaps split each .o file into several .o files each with only one section. Would it work? Would it make the resulting binary larger or inefficient? Another option could be to mark all symbols in libtee_core.a and other libaries as weak, but the problem here is that we already have some weak functions in TEE Core so this would break that. Perhaps if it would be possible to have different levels of weakness. Any ideas are welcome, either along this path or different approaches. Regards, Jens

11 years, 1 month

3
5
0 0

[ACTIVITY] 3 - 7 November 2014

by Omair Javaid

== Progress == AArch64 work on tracepoints and watchpoints failures [4/10] -- Review of AArch64 debug hardware architecture -- AArch64 debugging/testing stalled due to lab down time -- Tried compiling and running custom AArch64 kernel with foundation model Work on some arm specific fix of reverse-step and reverse-finish commands. [TCWG-498] [1/10] Miscellaneous [1/10] -- Meetings, Emails etc -- Prepared Hong Kong visa documents -- Annual Review 2014 Public Holidays [4/10] == Plan == Complete documents and travel to Islamabad for Hong Kong visa Resume AArch64 work on tracepoints and watchpoints failures with lab availability.

11 years, 1 month

1
0
0 0

[ACTIVITY] 3 - 7 November 2014

by Will Newton

== Progress == * Pushed malloc microbenchmark to glibc (1/10, TCWG-160) * Upstream work (4/10, CARD-341) - glibc patch review (C11 atomics series) - glibc patchwork cleanup * Look into binutils input fuzzing fixes (1/10) * Investigate ARM port of lld (2/10) * Email, meetings, review, etc. (2/10) == Issues == * Installed new cable modem. Seems to be working... == Plan == * Plan toolchain ILP32 work * lld investigation -- Will Newton Toolchain Working Group, Linaro

11 years, 1 month

1
0
0 0

[ACTIVITY] 3-7 November

by Charles Baylis

== Progress == Bug 404 [5/10] Bugs 403/418 [2/10] Misc [3/10] . office move . review

11 years, 1 month

1
0
0 0

[ACTIVITY] 3rd - 7th November

by Bernie Ogden

cbuild2 benchmarking - TCWG-360 [4/10] * SPEC 2006 cross-built binaries now running. Easy when you know how. libm exercising - CARD-1693 [4/10] * Understood improved libm usage on 1 benchmark. * Tried 3 more. 1 shows significantly more time in libm on AArch64 over AArch32. Meetings/mail/etc - [2/10] =Plan= cbuild2 benchmarking * Make sure reporting works * Get working in either LAVA or 'new TCWG infrastructure' * Test repeatability * Get SPEC 2000 working * Possibly have another go at building tools on AArch64 libm exerising * Keep working through the list of benchmarks * Hopefully reach the end and do some analysis

11 years, 1 month

1
0
0 0

[ACTIVITY] Week 45

by Yvan Roux

== Issues == * none. == Progress == * GCC 4.9 and 4.8 2014.11 (1/10) - Reviewed FSF branch Merges. * Lab move (3/10) - Cherry-picked cbuildv2 master patches in schroot-test - Created a new jenkins job to tst the "schroot lab move" branch - The job is able to build all the targets but validation still not works * Misc: (6/10) - Caught up with mails and irc logs - Prepared a patch that add __LINARO_[RELEASE|SPIN]__ macros. - Reviewed libatomic_ops upstream patch - Validate libunwind upstream patch - Various meetings. == Plan == * Back on backports * Tuesday off (11/11)

11 years, 1 month

1
0
0 0

[ACTIVITY] 3 - 7 November 2014

by Venkataramanan Kumar

= Progress == * TCWG-544 - Investigate core mark performance with both at -O3 with LTO + PGO (6/10) Different IPA inline decisions happening between Linaro and trunk. No major differences in other IPA passes. Trunk Inlines crcu32 and not inlines crcu16. Inlining crcu16 decreases instruction count. Honza pointed out a patch which inlines fucntions based on profile feedback and ignores max inlines parameters. It could be reason why trunk inlines crcu32 and then prevents inlining crcu16. Need to explore on this. * Bug fix - Linaro 849. Reproduced and tested it with trunk revision which fixes it. It looks to be same issue as upstream pr62308 (1/10) * Misc [3/10] Emails, linaro and AMD status meetings. 1-1 with inline mangers (Mev, Ryan). 1-1 with christophe. == Plan == * Debug and understand the inline differences trunk vs linaro compiler for core mark at -O3 with LTO + PGO. * Expecting one Aarch64 Enablement task. * Leave on 11/11/2014.

11 years, 1 month

1
0
0 0

[Weekly] 03-07 NOV 2014

by Michael Collison

== This week == * GCC Modularization Project (9/10) - Flattening header files - gimple-streamer.h, tree-streamer.h, lto-streamer.h - Additional updates based on review: - Created new header files to contain prototypes from .c files - Boostrapped changes - New changes being reviewed - tree-core.h, cfgloop.h, df.h - Removed unnecessary includes - Created new header files to contain exports from .c files * Misc. (1/10) - Conference calls == Next week == - Continue flattening of header files on GCC modularization project - Vacation November 12-14th

11 years, 1 month

1
0
0 0

[ACTIVITY] 3-7 November 2014

by Kugan

== Progress == * Zero/sign extension elimination with widening types (TCWG-546 - 9/10) - benchmarked Spec2k and the improvements are very small - Coremark fared worse. Looked into the cases and relaxed some of the constraints. - Subsequent passes are also not optimizing some of the expected cases - Re-factored and posted an RFC patch for comments at https://gcc.gnu.org/ml/gcc-patches/2014-11/msg00756.html * Improve block memory operations by GCC (TCWG-142 - 1/10) - Looked at the test-cases and gcc dumps == Plan == * Continue with improve block memory operations by GCC. * Continue with Zero/sign extension pass based on feedback.

11 years, 1 month

1
0
0 0

[ACTIVITY] 3-7 November 2014

by Christophe Lyon

== Progress == * GCC 4.8 and 4.9 releases (2/10) - committed both branch merges after review+checked the validation results - 4.8 needs another branch merge, to get the last errata-related backport * GCC trunk/4.9 cross-validation (1/10) - committed a couple of patches to clean the testsuite - observed a couple of regressions, no time to investigate/report * AArch64 sanitizer - got agreement in principle for a new patch, which would test the kernel headers version. * Neon intrinsics tests update (1/10) - the 2 PR I created last week are probably duplicate. - ARM posted patches to fix problems in the same area, but don't fix these PRs * cbuild2 - no progress * Misc (6/10) - calls, meetings, support == Next == - Tuesday 11th public holiday * AArch64 sanitizer * Neon intrinsics update * GCC linaro 4.8/4.9 releases * cbuild2: - analyze previous results - look at backport-test and tcwgweb scripts+logs

11 years, 1 month

1
0
0 0

[ACTIVITY] Week 45

by Renato Golin

== Progress == * Automation Framework (CARD-1378 4/8) - Moving TCWG machines to the new office - Setting up new rack, stacking boards, etc. - Setting up Junos * Buildbots (TCWG-76 2/8) - Moving buildbots to the new office - Checking libcxxabi failure, marking as XFAIL - All bots green * Background (2/8) - Code review, meetings, discussions, etc. * 1 day ill == Plan == * Continue lab migration

11 years, 1 month

1
0
0 0

GDB Build Regression

by Christopher Covington

Hi, When updating: >From git://git.linaro.org/toolchain/binutils-gdb e0f5246..336649d master -> linaro/master I now get the following build error: gdb/binutils/readelf.c: In function ‘process_mips_specific’: gdb/binutils/readelf.c:13522:3: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 2 has type ‘size_t’ [-Werror=format=] printf (_("<symbol index %lu exceeds number of dynamic symbols>"), i); ^ Thanks, Cov -- Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project

11 years, 1 month

2
1
0 0

[RFC] Linaro release version number macros

by Yvan Roux

Hi, after the recent lkml thread on blacklisting some GCC versions (see below) and the issue in identifying accurately our releases, I propose to add some Linaro specific macros in our branches (i.e this patch will not go upstream) to be able to check the Linaro version at preprocessor time. It will not solve the kernel issue with 4.8.N but hopefully help if such issues happen again the the futur. http://thread.gmane.org/gmane.linux.ports.arm.omap/119412 What GCC has for the moment is 3 macros __GNUC__, __GNUC_MINOR__ and __GNUC_PATCHLEVEL__ that are filled by parsing version number contained in BASE-VER file, for instance on our 4.9 branch: __GNUC__ = 4 __GNUC_MINOR__ = 9 __GNUC_PATCHLEVEL__ = 2 In our branches, the Linaro version number is in the LINARO-VERSION file and has this format: At release point : 4.9-2014.10 Head of our branch: 4.9-2014.10-1~dev I want your (the team and users) point of view on the macros we need to create from it. Here is the options I see: A - Be fully Linaro consistent: __LINARO_MAJOR__ = 4 __LINARO_MINOR__ = 9 __LINARO_YEAR__ = 2014 __LINARO_MONTH__ = 10 __LINARO_SPIN__ = 0 or N __LINARO_STATE = 0 for release or 1 for dev B - Only give information that are not in the __GNUC* macros: __LINARO_YEAR__ = 2014 __LINARO_MONTH__ = 10 __LINARO_SPIN__ = 0 or N __LINARO_STATE = 0 for release or 1 for dev C - Be more concise: __LINARO_VERSION__ = 201410 __LINARO_SPIN__ = 0 or N __LINARO_STATE = 0 for release or 1 for dev D - Even more: __LINARO_VERSION__ = 201410N (with N the spin number) __LINARO_STATE = 0 for release or 1 for dev E - Hardcore conciseness: __LINARO__ = 201410NM (N = SPIN M = state) F - One of the previous ones without STATE information. G - One of the previous ones without SPIN information. Do you think it is something we need ? Do we already have that kind of macros in some products (binutils, gdb, glibc, ...) ? What option do you prefer ? My own feeling is that C+F is sufficient as STATE information is useless for releases and I don't think dev builds checking have to be used in another project. But SPIN information can be useful has we're doing respin because an outstanding issue/improvement has to be fixed/added to the current release, thus it is the kind of thing you want to check if the version of the compiler you are using contains. Thanks, Yvan

11 years, 1 month

5
5
0 0

Will this ARM64 erratum patch be backported to this month's Linaro GCC 4.9 release?

by Panshilin (Peter)

Dear all concerned: ARM has reported it's 53's bug:AArch64 multiply-accumulate instruction might produce incorrect result and developed the patch descriped below. will the patch be backported to Linaro 4.9 this month's release. https://gcc.gnu.org/ml/gcc-cvs/2014-10/msg00335.html thanks Peter

11 years, 1 month

2
5
0 0

[ACTIVITY] 27th - 31st October

by Bernie Ogden

cbuild2 benchmarking - TCWG-360 [8/10] * Scripts build SPEC 2006 tools on x86_64 and arm, not yet on AArch64 * Scripts cross-build for x86 to arm and aarch64 * Cross-built binaries refuse to run Meetings/mail/etc - [2/10] =Plan= cbuild2 benchmarking * Make cross-built binaries run, collect reports * Build tools for AArch64 (lower priority) libm exerising * Work through list of benchmarks, see what I find

11 years, 1 month

1
0
0 0

[ACTIVITY] 27 - 31 October 2014

by Venkataramanan Kumar

= Progress == * TCWG-544 - Investigate core mark performance with both at -O3 with LTO + PGO (6/10) * Misc [3/10] emails, linaro and AMD meetings and 1-1 with inline manger. 1-1 with christophe. * Tried to reproduce Bug 63653 (1/10) == Plan == * Continue core mark performance with both at -O3 with LTO + PGO. * Continue Bugfix 63653

11 years, 1 month

1
0
0 0

[ACTIVITY] 27 - 31 October 2014

by Will Newton

== Progress == * Holiday on Monday (2/10) * Upstream work (4/10, CARD-341) - Patch review - Look into malloc hooks issue - Understand Cortex-A53 ld patch - Applied patches * Investigate libm optimization opportunities and benchmarks (2/10) * Email, meetings, review, etc. (2/10) == Issues == * None == Plan == * Follow up single thread optimization discussions * Finish review doc -- Will Newton Toolchain Working Group, Linaro

11 years, 1 month

1
0
0 0

[ACTIVITY] 27 - 31 October 2014

by Omair Javaid

== Progress == GDB Tracepoints/Fast Tracepoints support on arm [TCWG-480] [3/10] -- Investigate arm hardware debugging capabilities in linux kernel. ARM/AArch64 GDB testsuite failures investigation [TCWG-507] [4/10] Trying out patches that add support for gdbserver catch vfork/fork [TCWG-507] [2/10] Miscellaneous [1/10] -- Meetings, Emails etc -- Annual Review 2014 == Plan == Monday/Tuesday Public Holidays in Pakistan. Fix watchpoints-reuse-slot tests for arm somehow to allow skipping unsupported tests Also investigate the same on AArch64. [TCWG-507] Re-submit some hanging patches after a bit of rework to grab attention.

11 years, 1 month

1
0
0 0

[Weekly] 27-31 OCT 2014

by Michael Collison

== This week == * GCC Modularization Project (7/10) - Decided on work near term work objectives with Andrew Macleod - Began flattening header files - gimple-streamer.h (complete) - tree-streamer.h (complete) - lto-streamer.h (complete) - tree-core.h (In progress) - cfgloop.h (In Progress - df.h (In progress) * Vector Extensions Project (2/10) - Design work on C++ classes - Call with Charles Baylis to discuss libvpx benchmark * Misc. (1/10) - Conference calls - ARM required online training == Next week == - Continue flattening of header files on GCC modularization project - Further review of libvpx and vector extensions design work

11 years, 1 month

1
0
0 0

[ACTIVITY] 27-31 October 2014

by Kugan

== Progress == * Zero/sign extension elimination with widening types (TCWG-546 - 10/10) - Fixed regression failures - Fixed bootstrapping issues for ARM and AArch64 - Re-factored and added some comments - x86-64 Bootstrapped and regression tested for all languages with forced promotion. There is 6 differences in scanning for certain instructions. All the execution tests are passing. Needs further investigation. == Plan == * Continue with Zero/sign extension pass. - Benchmarking - Get patch ready for upstream discussion * Improve block memory operations by GCC (TCWG-142) - Start work on this

11 years, 1 month

1
0
0 0

[ACTIVITY] 27-31 October 2014

by Christophe Lyon

== Progress == * GCC trunk/4.9 cross-validation (1/10) - submitted a couple of patches to clean testsuite cases * Neon intrinsic tests (1/10) - submitted patch to avoid running the tests on ARM targets w/o Neon - started adding new tests - created 2 PR about intrinsic tests failing on AArch64_be (1 assigned to Venkat, 1 to me) * AArch64 sanitizer (1/10) - submitted a patch upstream to allow supporting both older and newer kernels No feedback so far. * GCC 4.8 and 4.9 releases (3/10) - preparing both releases including ARM's latest fixes for the A53 erratum - had to respin mid-week after new fix was committed - LINK_SPEC patch not committed yet in 4.8, and committed in 4.9 after I made the branch merge. - now checking results with references. Several FAIL appear. TBC. * cbuild2 schroot and master branches comparison (1/10) - re-ran schroot branch after cleaning spurious "-static" flag left in dejagnu configuration - better results, faster * Misc (3/10) - calls, meetings == Next == * GCC 4.8 and 4.9 releases: hopefully, after branch merge review * AArch64 sanitizer * Neon intrinsics tests update * cbuild2: - analyze previous results - look at backport-test and tcwgweb scripts + logs

11 years, 1 month

1
0
0 0

[ACTIVITY] Week 44

by Renato Golin

== Progress == * US LLVM Dev Mtg (4/6) * Buildbots (TCWG-76 1/6) - Fixing last bugs of the libcxx bot - One last failure being looked at * Background (1/6) - Code review, meetings, discussions, etc. - Meeting with Google/ARM/Qualcomm about Android+LLVM * Two days off == Plan == * Investigate last libcxx bug * Move lab/office

11 years, 1 month

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain