- linaro-toolchain - lists.linaro.org

[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

10 years, 7 months

1
0
0 0

[ACTIVITY] Week 47

by Renato Golin

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

10 years, 7 months

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.

10 years, 7 months

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

10 years, 7 months

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

10 years, 7 months

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

10 years, 7 months

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.

10 years, 7 months

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

10 years, 7 months

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.

10 years, 7 months

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

10 years, 7 months

1
0
0 0

[ACTIVITY] Week 46

by Renato Golin

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

10 years, 7 months

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)

10 years, 7 months

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.

10 years, 7 months

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

10 years, 7 months

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

10 years, 7 months

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.

10 years, 7 months

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

10 years, 7 months

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

10 years, 7 months

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

10 years, 7 months

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)

10 years, 7 months

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.

10 years, 7 months

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

10 years, 7 months

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.

10 years, 7 months

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

10 years, 7 months

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

10 years, 7 months

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

10 years, 7 months

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

10 years, 7 months

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

10 years, 7 months

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

10 years, 8 months

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

10 years, 8 months

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

10 years, 8 months

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.

10 years, 8 months

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

10 years, 8 months

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

10 years, 8 months

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

10 years, 8 months

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

10 years, 8 months

1
0
0 0

Re: linaro-toolchain Digest, Vol 52, Issue 16

by 박주형

Thanks for the reply, Will Newton. Then can we expect the fix to be included for the official Android toolchain 2014.11? And, thanks for explaining the culprit of this bug, Jongsung Kim! :) On Wed, Oct 29, 2014 at 9:00 PM, <linaro-toolchain-request(a)lists.linaro.org> wrote: > Send linaro-toolchain mailing list submissions to > linaro-toolchain(a)lists.linaro.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.linaro.org/mailman/listinfo/linaro-toolchain > or, via email, send a message with subject or body 'help' to > linaro-toolchain-request(a)lists.linaro.org > > You can reach the person managing the list at > linaro-toolchain-owner(a)lists.linaro.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of linaro-toolchain digest..." > > > Today's Topics: > > 1. RE: Enabling back linker plugin for Linaro Android toolchain > (Jongsung Kim) > 2. Re: Enabling back linker plugin for Linaro Android toolchain > (Will Newton) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 29 Oct 2014 11:26:30 +0900 > From: "Jongsung Kim" <neidhard.kim(a)lge.com> > To: '???' <qkrwngud825(a)gmail.com>, <linaro-android(a)lists.linaro.org>, > <linaro-toolchain(a)lists.linaro.org> > Subject: RE: Enabling back linker plugin for Linaro Android toolchain > Message-ID: <012f01cff31f$c01cea90$4056bfb0$(a)lge.com> > Content-Type: text/plain; charset="UTF-8" > > The version-string from binutils-linaro looks to be blamed. It once was: > > GNU ld (crosstool-NG linaro-1.13.1-4.7-2013.04-20130415 - Linaro GCC > 2013.04) 2.23.1 > > and the linker plugin works with this version of Linaro prebuilt > toolchain. Now it is: > > GNU ld (crosstool-NG linaro-1.13.1-4.8-2014.04 - Linaro GCC 4.8-2014.04) > 2.24.0.20140311 Linaro 2014.03 > GNU ld (crosstool-NG linaro-1.13.1-4.9-2014.08 - Linaro GCC 4.9-2014.08) > 2.24.0.20140801 Linaro 2014.08 > > and the linker plugin is not supported: > > $ arm-linux-gnueabihf-gcc -flto -fuse-linker-plugin -o hello hello.c > arm-linux-gnueabihf-gcc: error: -fuse-linker-plugin is not supported in > this configuration > > Look into gcc/configure script. It uses the version of ld to determine > whether ld supports linker plugin. It extracts the version by doing > something like: > > $ arm-linux-gnueabihf-ld --version | sed 1q | sed -n -e 's,^.*[ > ]$[0-9][0-9]*\.[0-9][0-9]*.*$$,\1,p' > > and it will extract the last 2014.03 or 2014.08. By using proper > substitution expression like 's,^GNU ld (.*) $[0-9][.0-9]*$.*$,\1,p', the > script may enable linker plugin. > > However, patching the script looks like a bad idea, because it doesn?t > help handling the version of gold: > > GNU gold (GNU Binutils for Ubuntu 2.24) 1.11 > GNU gold (crosstool-NG linaro-1.13.1-4.7-2013.04-20130415 - Linaro GCC > 2013.04 2.23.1) 1.11 > GNU gold (crosstool-NG linaro-1.13.1-4.8-2014.04 - Linaro GCC 4.8-2014.04 > 2.24.0.20140311 Linaro 2014.03) 1.11 > GNU gold (crosstool-NG linaro-1.13.1-4.9-2014.08 - Linaro GCC 4.9-2014.08 > 2.24.0.20140801 Linaro 2014.08) 1.11 > > I couldn?t find a reasonable general expression to extract the version. > > > From: linaro-toolchain-bounces(a)lists.linaro.org [mailto: > linaro-toolchain-bounces(a)lists.linaro.org] On Behalf Of ??? > Sent: Monday, October 27, 2014 10:15 PM > To: linaro-android(a)lists.linaro.org; linaro-toolchain(a)lists.linaro.org > Subject: Enabling back linker plugin for Linaro Android toolchain > > I'm using Linaro Android toolchain's arm-eabi- for compiling my Android > Linux kernel with LTO. > > The main benefits of my kernel is that it uses > LTO(Link-Time-Optimizations). > (Patches found here: https://github.com/andikleen/linux-misc) > > But now, it's broken with Linaro Android toolchains from 2014.09~ > > Building Linux kernel with LTO requires Linker plugin with the toolchain. > > > But for some reason, linker plugin is disabled with 2014.09 and 2014.10 > (Which I used from here : > https://android-build.linaro.org/builds/~linaro-android/toolchain-4.9-2014.… > https://android-build.linaro.org/builds/~linaro-android/toolchain-4.9-2014.… > ) > > LTO build works flawlessly with 2014.08. > > With 2014.09 and 2014.10, I get the following error : > cc1: error: -fno-fat-lto-objects are supported only with linker plugin > > If I explicitly remove " -fno-fat-lto-objects " from the Makefile, the > linker fails to link all of the object files. > > > I would like to ask Linaro to enable back the Linker plugin support :) > > Thanks in advance.. > > > > > ------------------------------ > > Message: 2 > Date: Wed, 29 Oct 2014 09:12:53 +0000 > From: Will Newton <will.newton(a)linaro.org> > To: Jongsung Kim <neidhard.kim(a)lge.com> > Cc: ??? <qkrwngud825(a)gmail.com>, linaro-android(a)lists.linaro.org, > Linaro Toolchain <linaro-toolchain(a)lists.linaro.org> > Subject: Re: Enabling back linker plugin for Linaro Android toolchain > Message-ID: > <CANu=DmhPdCGYw0=hCs9tmkbCU6hMLLMJnYS-u_JGz= > p17Bgonw(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On 29 October 2014 02:26, Jongsung Kim <neidhard.kim(a)lge.com> wrote: > > The version-string from binutils-linaro looks to be blamed. It once was: > > > > GNU ld (crosstool-NG linaro-1.13.1-4.7-2013.04-20130415 - Linaro GCC > 2013.04) 2.23.1 > > > > and the linker plugin works with this version of Linaro prebuilt > toolchain. Now it is: > > > > GNU ld (crosstool-NG linaro-1.13.1-4.8-2014.04 - Linaro GCC 4.8-2014.04) > 2.24.0.20140311 Linaro 2014.03 > > GNU ld (crosstool-NG linaro-1.13.1-4.9-2014.08 - Linaro GCC 4.9-2014.08) > 2.24.0.20140801 Linaro 2014.08 > > > > and the linker plugin is not supported: > > > > $ arm-linux-gnueabihf-gcc -flto -fuse-linker-plugin -o hello hello.c > > arm-linux-gnueabihf-gcc: error: -fuse-linker-plugin is not supported in > this configuration > > > > Look into gcc/configure script. It uses the version of ld to determine > whether ld supports linker plugin. It extracts the version by doing > something like: > > > > $ arm-linux-gnueabihf-ld --version | sed 1q | sed -n -e 's,^.*[ > ]$[0-9][0-9]*\.[0-9][0-9]*.*$$,\1,p' > > > > and it will extract the last 2014.03 or 2014.08. By using proper > substitution expression like 's,^GNU ld (.*) $[0-9][.0-9]*$.*$,\1,p', the > script may enable linker plugin. > > > > However, patching the script looks like a bad idea, because it doesn?t > help handling the version of gold: > > > > GNU gold (GNU Binutils for Ubuntu 2.24) 1.11 > > GNU gold (crosstool-NG linaro-1.13.1-4.7-2013.04-20130415 - Linaro GCC > 2013.04 2.23.1) 1.11 > > GNU gold (crosstool-NG linaro-1.13.1-4.8-2014.04 - Linaro GCC > 4.8-2014.04 2.24.0.20140311 Linaro 2014.03) 1.11 > > GNU gold (crosstool-NG linaro-1.13.1-4.9-2014.08 - Linaro GCC > 4.9-2014.08 2.24.0.20140801 Linaro 2014.08) 1.11 > > > > I couldn?t find a reasonable general expression to extract the version. > > This should be fixed in binutils-linaro-2.24-2014.11. > > > From: linaro-toolchain-bounces(a)lists.linaro.org [mailto: > linaro-toolchain-bounces(a)lists.linaro.org] On Behalf Of ??? > > Sent: Monday, October 27, 2014 10:15 PM > > To: linaro-android(a)lists.linaro.org; linaro-toolchain(a)lists.linaro.org > > Subject: Enabling back linker plugin for Linaro Android toolchain > > > > I'm using Linaro Android toolchain's arm-eabi- for compiling my Android > Linux kernel with LTO. > > > > The main benefits of my kernel is that it uses > LTO(Link-Time-Optimizations). > > (Patches found here: https://github.com/andikleen/linux-misc) > > > > But now, it's broken with Linaro Android toolchains from 2014.09~ > > > > Building Linux kernel with LTO requires Linker plugin with the toolchain. > > > > > > But for some reason, linker plugin is disabled with 2014.09 and 2014.10 > > (Which I used from here : > https://android-build.linaro.org/builds/~linaro-android/toolchain-4.9-2014.… > https://android-build.linaro.org/builds/~linaro-android/toolchain-4.9-2014.… > ) > > > > LTO build works flawlessly with 2014.08. > > > > With 2014.09 and 2014.10, I get the following error : > > cc1: error: -fno-fat-lto-objects are supported only with linker plugin > > > > If I explicitly remove " -fno-fat-lto-objects " from the Makefile, the > linker fails to link all of the object files. > > > > > > I would like to ask Linaro to enable back the Linker plugin support :) > > > > Thanks in advance.. > > > > > > _______________________________________________ > > linaro-toolchain mailing list > > linaro-toolchain(a)lists.linaro.org > > http://lists.linaro.org/mailman/listinfo/linaro-toolchain > > > > -- > Will Newton > Toolchain Working Group, Linaro > > > > ------------------------------ > > _______________________________________________ > linaro-toolchain mailing list > linaro-toolchain(a)lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-toolchain > > > End of linaro-toolchain Digest, Vol 52, Issue 16 > ************************************************ >

10 years, 8 months

1
0
0 0

Enabling back linker plugin for Linaro Android toolchain

by 박주형

I'm using Linaro Android toolchain's arm-eabi- for compiling my Android Linux kernel with LTO. The main benefits of my kernel is that it uses LTO(Link-Time-Optimizations). (Patches found here: https://github.com/andikleen/linux-misc) But now, it's broken with Linaro Android toolchains from 2014.09~ Building Linux kernel with LTO requires Linker plugin with the toolchain. But for some reason, linker plugin is disabled with 2014.09 and 2014.10 (Which I used from here : https://android-build.linaro.org/builds/~linaro-android/toolchain-4.9-2014.… https://android-build.linaro.org/builds/~linaro-android/toolchain-4.9-2014.… ) LTO build works flawlessly with 2014.08. With 2014.09 and 2014.10, I get the following error : cc1: error: -fno-fat-lto-objects are supported only with linker plugin If I explicitly remove " -fno-fat-lto-objects " from the Makefile, the linker fails to link all of the object files. I would like to ask Linaro to enable back the Linker plugin support :) Thanks in advance..

10 years, 8 months

3
2
0 0

Linaro Lab Maintenance impacts to the November Toolchain Quarterly release

by Ryan Arnold

Hi All, There will be lab downtime in the month of November, and rather than jeopardize the November quarterly binary toolchain release we've decided to take some steps to ensure that it takes place on time. The November binary toolchain quarterly release will contain some ARM64 erratum fixes. These are already in the Linaro GCC 4.9 2014.10 source package release. The November binary toolchain quarterly release will contain these fixes, and will be delivered as planned, but will be based on the Linaro GCC 4.9 2014.10 package. We will not have a November Linaro GCC 4.9 2014.11 source package release. The December release will be the next Linaro GCC 4.9 source package release. -- Ryan S. Arnold Linaro Toolchain Working Group - Engineering Manager www.linaro.org

10 years, 8 months

1
0
0 0

[ACTIVITY] 20th - 24th October

by Bernie Ogden

cbuild2 benchmarking - TCWG-360 [2/10] * Figured out how to cook my own OE images * Started remembering how to build spec libm exercising - CARD-1693 [2/10] * Borrowed a usable Juno * Found that lapack tests segfault on AArch64 * Ran linpack hpl, didn't observe it exercising libm much ** Haven't ruled out Bernie-error yet, though Upstream - CARD-341 [1/10] * Respun lowlevellock.h comments Meetings/mail/etc [5/10] * A lot of time (>3/10) in performance review and other annual ARM admin * Some back and forth about difficulties of userspace access to ID registers =Plan= Get spec2006 working via my scripts Find a good HPL libm exerciser Spend a lot less time on ARM admin

10 years, 8 months

2
1
0 0

[ACTIVITY] 20 - 24 October 2014

by Omair Javaid

== Progress == Further progress on GDB Tracepoints/Fast Tracepoints support on arm [TCWG-480] [6/10] -- Debugging and trying out some code enabling tracepoints in gdbserver -- Research on past tracepoint patches and x86 vs arm architecture comparison ARM/AArch64 GDB testsuite failures investigation [2/10] Miscellaneous [2/10] -- Meetings, Emails etc -- Fix SSH configurations -- Patch Scrolling -- Hong Kong visa process -- Multiple Dr visits due to continued sickness == Plan == Further progress on GDB Tracepoints/Fast Tracepoints support on arm [TCWG-480] Fix internet latency issues from lab hardware.

10 years, 8 months

1
0
0 0

[ACTIVITY] 20 - 24 October 2014

by Venkataramanan Kumar

= Progress == * Short week was in vacation (22-24 October) * Updated perf profile numbers for instruction count and documented my analysis for Linaro compiler's O3 + LTO comparison on Aarch64 vs X86_64 (TCWG-544) (2/10) * Misc [2/10] emails, AMD meetings and 1-1 with inline manger. 1-1 with christophe. == Plan == * Coremark benchmark and profiling. Investigate trunk degradation for O3+ PGO + LTO and report.

10 years, 8 months

1
0
0 0

[ACTIVITY] 20 - 24 October 2014

by Kugan

== Progress == * Zero/sign extension elimination with widening types (TCWG-546 - 10/10) - Re-wrote the pass from the results of experiments so far - Fixed most of the regression failures - 5 tests are still failing from C/C++/Fortran regression suite. == Plan == * Continue with Zero/sign extension pass. - Get bootstrapping for ARM and AArch64 working - Fix remaining regression failures - Add detail dumps - Remove unnecessary copies (it is now being removed dead code elimination pass) - Get patch ready for upstream discussion

10 years, 8 months

1
0
0 0

[Weekly] 20-24 OCT 2014

by Michael Collison

== This week == * GCC Modularization Project (5/10) - Reviewed Re-Architecture GNU Cauldron videos by Andrew Macleod - Reviewed tree/gimple source base * Linaro bugzilla 602 - gcc 4.7.3 compiler internal error while building hsail components (2/10) - Resolved bug by determining that 4.7 compiler was assinging a incorrect VFP register to a parameter - Issue was fixed in 4.8 by adding call to arm_hard_regno_ok which disallowed register * vector Extensions Project (2/10) - Preliminary design work on C++ classes and libvpx review * Misc. (1/10) - Conducted interview with Prathamesh Kulkarni - Conference calls == Next week == - GCC Modularization draft plan to TCWG group for review - Understand status of Re-Architecture work by Andrew Macleod - Further review of libvpx and vector extensions design work

10 years, 8 months

2
1
0 0

[ACTIVITY] Week 43

by Charles Baylis

=== Progress === SPEC Benchmarking [5/10] . managed to run SPEC2k . managed to run integer parts of SPEC2k6 . spec2xxx-report fails . can't run full suite as LAVA Junos have insufficient disk NEON error reporting bugs #403/#418 [3/10] . ongoing mailing list discussions vldN_lane patches [1/10] . respun and committed Misc [1/10] === Plan === Talk to Tejas @ ARM about AArch64 NEON loads/stores Review prep Move office Day off at some point (likely Wednesday)

10 years, 8 months

1
0
0 0

[ACTIVITY] 20-24 October 2014

by Christophe Lyon

Short week, 2 days off == Progress == * GCC trunk/4.9 cross-validation (2/10) - committed testsuite patch to support forcing -mword-relocations option when compiling testglue.c * Neon intrinsics tests (2/10) - committed the 1st batch (21 commits) * AArch64 sanitizer - libsanitizer internal data depend on the kernel headers version used to build the toolchain, old_[gu]id_t type changed in 3.15.3. - discussing the best way to address this * Misc (2/10) - calls, meetings == Next == * 4.8 branch merge for next release * GCC trunk/4.9 cross-validation - investigate abi_check test, probably another testsuite harness configuration issue * AArch64 sanitizer * Neon intrinsics tests update * cbuild2: - analyze previous results - look at backport-test script + logs

10 years, 8 months

1
0
0 0

[ACTIVITY] Week 43

by Renato Golin

== Progress == * Automation Framework (CARD-1378 1/10) - Setting up Junos with ARM * Toolchain (CARD-862 1/10) - Some progress on fpu parser issue - Produced a lot more work for the near future * Buildbots (TCWG-76 4/10) - Setting up a libc++ buildbot, working on reducing failures - Some bots broken, bisecting * Background (4/10) - Code review, meetings, discussions, etc. - Annual review - More lab move planning - EuroLLVM meetings and planning == Plan == * US LLVM whole next week

10 years, 8 months

1
0
0 0

[ACTIVITY] 20 - 24 October 2014

by Will Newton

== Progress == * Released Linaro glibc 2.20 2014.11 (2/10) * Released Linaro binutils 2.24 2014.11-2 (2/10) * Investigate gdb and Coresight integration possibilities (1/10) * Email, meetings, etc. (1/10) * Upstream work (4/10, CARD-341) - Patch review - Look binutils testsuite failures on ARM, submit patch == Issues == * None == Plan == * Monday off * Support release process -- Will Newton Toolchain Working Group, Linaro

10 years, 8 months

1
0
0 0

[ANNOUNCE] Linaro GCC 4.9 2014.10 released

by Yvan Roux

The Linaro Toolchain Working Group (TCWG) is pleased to announce the 2014.10 release of the Linaro GCC 4.9 source package. Linaro GCC 4.9 2014.10 is the seventh Linaro GCC source package release. It is based on FSF GCC 4.9.2-pre+svn216130 and includes performance improvements and bug fixes. 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 enginering[2] releases. Interesting changes in this GCC source package release include * Updates to GCC 4.9.2-pre+svn216130 * Backport of [AArch64] Define TARGET_FLAGS_REGNUM * Backport of PR target/61565 * Backport of [AArch64] libitm: Improve _ITM_beginTransaction * Backport of [AArch64] Fix *extr_insv_lower_reg<mode> pattern * Backport of [AArch64] Use CC_Z and CC_NZ with csinc and similar instructions * Backport of [AArch32] Implement and vectorize lceil, lfloor, lround optabs with new ARMv8-A instructions * Backport of [AArch64] Improve epilogue unwind info rth * Backport of [AArch64] Add a mode to operand 1 of sibcall_value_insn * Backport of [AArch64] Add a builtin for rbit(q?)_p8; add intrinsics and tests * Backport of [AArch32/AArch64] Schedule alu_ext for Cortex-A53 * Backport of [AArch64] Remove varargs from aarch64_simd_expand_args * Backport of [AArch64] Tidy: remove unused qualifier_const_pointer * Backport of [AArch32/AArch64] Add scheduling info for ARMv8-A FPU new instructions in Cortex-A53 * Backport of [AArch32] Convert FP mnemonics to UAL. * Backport of [AArch32] Enable auto-vectorization for copysignf * Backport of [AArch32][tests] Make input and output arrays 128-bit aligned in vectorisation tests * Backport of [AArch64] Add crtfastmath * Backport of PR target/56846 libstdc++ * Backport of PR target/63209 * Backport of [Ree] Ensure inserted copy don't change the number of hard registers * Backport of [AArch64] Fix force_simd macro in vdup_lane_2 * Backport of [AArch32] Disallow -mfpu=neon for unsuitable architectures * Backport of [AArch32] movmisalign<mode>_neon_load * Backport of [AArch64] Add constraint letter for stack_protect_test pattern * Backport of [AArch64] Auto-generate the "BUILTIN_" macros 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.

10 years, 8 months

2
2
0 0

Q about using AArch64 gdb with target running in AArch32 state

by Qu, Strong

Hi, I start to use Linary AArch64 toolchain recently and just joined this maillist. I went through some of the archived threads but didn't read all of them. So bear me if I'm asking dumb question or old question which had been answered before. For our use case, we are running the gdb client at early state of boot. So the ARMv8 target might be running into any EL and into either AArch64 or AArch32 state. My questions are: 1) Is the aarch64-none-elf-gdb.exe good for both AArch64 and AArch32 or I have to run the arm-none-eabi-gdb.exe if the target running in AArch32 state? 2) If the target is in AArch64 state, can I use the aarch64-none-elf-gdb.exe to load binary built for AArch32 to the target? I'm really appreciated if anybody can help me on these two questions. Thanks in advance, StrongQ

10 years, 8 months

3
2
0 0

[ACTIVITY] 13th - 17th October

by Bernie Ogden

cbuild2 benchmarking - TCWG-360 [3/10] * A few small enhancements and bug-fixes * Tried to run spec2006 on Juno, looks tricky libm profiling - CARD-1693 [3/10] * Pulled together lapack + blas * Looked a bit at how it exercises libm on x86 * Tried to look at how it exercises libm on Juno, looks tricky Meetings/mail/etc [4/10] * Featuring some fun with backups and ARM performance review season =Plan= * cbuild2 benchmarking - keep chipping away at spec/juno * libm profiling - attempt to assemble an AArch64 setup that works for me * further performance review/corporate admin will take up extra time this week, but should then fall back to normal levels =Issues= State of the setup on our Junos

10 years, 8 months

1
0
0 0

[Activity] Oct 13-19

by Rob Savoye

== Progress == * Part way through integrating Cbuild2/Jenkins with Gerrit. (#1692, 8/10) - Implemented functions to use the REST API to Gerrit via SSH. - Integrated into build and test processes. * Meetings and Misc (2/10) - Ordered 10 Snapdragon boards == Plan == * Finish Gerrit integration with Cbuild2 and Jenkins. (#1692) - Find a way the buildslave user can use the SSH connection to Gerrit. * Start merging the linaro branch in DejaGnu to master to get ready for the next release. * Start getting ready for the lab move, do what I can ahead of time. == Issues == * Gerrit comments via REST strip out all newlines, so I need to limit the message size after a test run.

10 years, 8 months

1
0
0 0

[ACTIVITY] 13 October 2014 to 17 October 2014.

by Venkataramanan Kumar

= Progress == * Core mark benchmark and report for PGO and PGO + LTO (TCWG-544) (6/10) Going by CPU cycles adding LTO gains in x86 and degrades in Aarch64 . Looked at hot functions and examining assembly the code generation seems to be same. X86_64 does alignment of code. Also branch misses decreased in X86_64 compared to Aarch64 with -flto + -O3. Also profiled for instruction counts on Aarch64 with linaro compiler. These profiles say that we are executing less instructions with LTO and PGO for Aarch64. * PR 63173- Reproduced the issue and changed the test case to work with trunk. Now Looks like someone else has a patch for it. (1/10). so will work on other bugs. * Misc [3/10] Internal work, emails, AMD meetings and 1-1 with inline manger. 1-1 with Maxim, christophe and 1-1 with ryan == Plan == * Coremark benchmark and profiling. Investigate trunk degradation for O3+ PGO + LTO and report. == leaves == Diwali holiday (22-24)

10 years, 8 months

1
0
0 0

[ACTIVITY] Week 42

by Charles Baylis

== Progress == Sick leave [2/10] Patch submission for vldN_lane [1/10] Attempting to run SPEC2k6 on Juno [6/10] Misc [1/10] irc support, openjdk suspected compiler bug, meetings, mailing lists

10 years, 8 months

1
0
0 0

[ACTIVITY] Week 42

by Yvan Roux

== Issues == * Still no network at home and will not be fixed before at least one week :( == Progress == * GCC 4.9 2014.10 (8/10) - Merged FSF 4.9 branch - Released Linaro 4.9 2014.10 * Misc: (2/10) - Various meetings. == Plan == * Analyse some failures that occur only in --enable-release.

10 years, 8 months

1
0
0 0

[ACTIVITY] 13 - 17 October 2014

by Omair Javaid

== Progress == Catch up with work after return from Eid ul Adha and Annual Holidays [7/10] * Hong Kong visa application * UPS repairs and office cleanup * Catching up with work, gdb roadmap and open/running cards. * Emails/Patch scrolling/Meetings etc * Sick day off on Monday GDB Tracepoints/Fast Tracepoints support on arm [TCWG-480] [3/10] * Getting re-synced with code where I left. == Plan == Further progress on GDB Tracepoints/Fast Tracepoints support on arm [TCWG-480] Investigate possibility of AArch64 trace-point work without availability of hardware. Check for GDB status on ARM and AArch64 vs x86.

10 years, 8 months

1
0
0 0

[Weekly] 13-17 OCT 2014

by Michael Collison

== This week == * GCC Modularization Project (5/10) - Reviewed previous documentation by Joseph Meyers - Reviewed source base to understand issues * Linaro bugzilla 602 - gcc 4.7.3 compiler internal error while building hsail components (3/10) - Reproduced with 4.7. Triage indicates coding error (operands reversed) - Continuing investigation to determine if issue exists with 4.8 and 4.9 * Linaro bugzilla 539 - .LTHUNK symbols are surviving (1/10) - Preliminary investigation and triage * Misc. (1/10) - Conference calls == Next week == - Draft plan for GCC modularization for review - Resolve bugzilla 602 - Continue investigation of bugzilla 602 - conduct interview with Prathamesh Kulkarni

10 years, 8 months

1
0
0 0

[ACTIVITY] 13 - 17 October 2014

by Kugan

== Progress == * Zero/sign extension elimination with widening types (TCWG-546 - 9/10) - Fixed ICEs and now can build the cross compiler and do the regression testing with qemu - some test-cases are failing due to condition that rely on overflow; this need fixing. - Bootstrapping on AArch64 still fails (but much later than previously). - Verified CRC is optimized * Improve block memory operations by GCC (TCWG-142 - 1/10) - Looked at the changes since the card was drafted == Plan == * Continue with Zero/sign extension pass.

10 years, 8 months

1
0
0 0

[ACTIVITY] 13-17 October 2014

by Christophe Lyon

== Progress == * GCC trunk/4.9 validation (CARD-647) (3/10) - committed testsuite patch to test if -shared is supported - forcing -mword-relocations flags when compiling testglue works on my Ubuntu machines, but does not in the Compute Farm RHEL5 servers. - investigating why, all the more as it made me incorrectly report failures in the 4.9 branch * Validation (2/10) - compared cbuild2 schroot-test branch and master the results of this manual run does not seem to match Jenkins results * Neon intrinsics tests (1/10) - fixed .exp harness to support parallelization - looking at how to pre-support fp16, will probably skip it for now, and add dedicated tests later * AArch64 sanitizer (1/10) - GCC trunk seems to need to cherry pick a sanitizer patch when building using recent kernel headers - tried to use Jenkins to build trunk and trunk+cherry-pick, but the results are not consistent needs more investigation * Misc (3/10) - calls, meetings, irc == Next == * GCC trunk/4.9 cross-validation - fix -mword-relocations support - investigate abi_check test * AArch64 sanitizer * Neon intrisics tests update * cbuild2: - analyze previous results (mostly check the logs....) - look at backport-test script + logs Short next week: off Wednesday/Thursday

10 years, 8 months

1
0
0 0

[ACTIVITY] 13 - 17 October 2014

by Will Newton

== Progress == * Respin of malloc single-thread optimizations (4/10, TCWG-436) - Create a generic header, include AArch64 in series * Further work on malloc app benchmark framework (4/10, TCWG-441) - Cleaned up, improved reliability, added comments - Committed to cortex-malloc.git * Email, meetings, etc. (1/10) * Upstream work (1/10, CARD-341) - glibc patch review and pings - Look into some bug reports and testsuite failures == Issues == * Electricians and gas engineers turning off power/heating at various points == Plan == * Hopefully get some resolution of single thread atomic stuff for glibc -- Will Newton Toolchain Working Group, Linaro

10 years, 8 months

1
0
0 0

[ACTIVITY] Week 42

by Renato Golin

== Progress == * Linux Plumbers (6/10) - Attended conference, Android/Tools/LLVM tracks - Presented 2 talks (GCC+LLVM and LLVM+ARM) * Buildbots (TCWG-76 2/10) - Made the Compiler-RT bot green! Now on to the libc++ one * Background (2/10) - Code review, meetings, discussions, etc. - Internet upgrade, re-wiring the house, building works == Plan == * Add libc++abi buildbot * Follow up on the fpu issues on Clang/asm

10 years, 8 months

1
0
0 0

Prebuilt binary download for gcc-linaro 4.8.4

by Rick Liu

Hi, In release 14.08, Linaro GCC 4.8 2014.08 is based off GCC 4.8.4+svn213802. [http://releases.linaro.org/14.08/components/toolchain/gcc-linaro/4.8] However, in toolchain/binaries, [http://releases.linaro.org/14.08/components/toolchain/binaries] I can't find the download for the prebuilt binaries for gcc-linaro-arm-linux-gnueabihf-4.8. I only found the download for 4.9 version. It seems the last 4.8 version binary existed in 2014.04 release only? [http://releases.linaro.org/14.04/components/toolchain/binaries] Where can I get the prebuilt binary of gcc-linaro-arm-linux-gnueabihf-4.8-2014.08_linux.tar.bz2? Thanks, Rick

10 years, 8 months

1
0
0 0

Re: [PATCH] ARM: Blacklist GCC 4.8.0 to GCC 4.8.2 - PR58854 (fwd)

by Nicolas Pitre

FYI. The whole thread is available here: http://article.gmane.org/gmane.linux.ports.arm.omap/119412 ---------- Forwarded message ---------- Date: Thu, 16 Oct 2014 01:18:01 +0100 From: Russell King - ARM Linux <linux(a)arm.linux.org.uk> To: Peter Hurley <peter(a)hurleysoftware.com> Cc: Nathan Lynch <Nathan_Lynch(a)mentor.com>, David Laight <David.Laight(a)ACULAB.COM>, Otavio Salvador <otavio(a)ossystems.com.br>, Linus Torvalds <torvalds(a)linux-foundation.org>, Nicolas Pitre <nico(a)fluxnic.net>, Linux OMAP Mailing List <linux-omap(a)vger.kernel.org>, linux-arm-kernel(a)lists.infradead.org Message-ID: <20141016001801.GQ12379(a)n2100.arm.linux.org.uk> Subject: Re: [PATCH] ARM: Blacklist GCC 4.8.0 to GCC 4.8.2 - PR58854 On Wed, Oct 15, 2014 at 06:18:30PM -0400, Peter Hurley wrote: > On 10/15/2014 05:56 PM, Russell King wrote: > > I was in two minds whether to include 4.8.3 as Linaro released a buggy > > toolchain which identifies itself as 4.8.3, but I decided that's also > > a distro problem. IMHO Linaro should really think about taking that > > compiler down given the seriousness of this bug and it being > > indistinguishable from the fixed stock version. > > Maybe it's unfair to blame them; Linaro just took a snapshot and > released what was there. > > If gcc is going to retain the "change release number then add all the > new features" model, some kind of prerelease indicator would help > eliminate this kind of problem. And that indicator should be both > a preprocessor define and parseable from the command line :) My comment is not to attribute blame to them, my comment is entirely on a technical level. My reasoning is that the bug is just as prevalent in userspace, though it will occur less often. Any program which uses signal handlers is a candidate for exactly the same kind of corruption, since you can receive that signal between the point that the stack pointer is modified and the function loads the parent context. Of course, there are ways around that: don't use signal handlers, or if you do, use alternate signal stacks. Neither of those can be guaranteed for any program though. So, let me put this another way: a compiler with this bug is _completely_ unsuitable for use for compiling programs for use under the Linux kernel _as well_ as the Linux kernel itself. The difference is that the Linaro compilers come with an expectation that they are usable on ARM... whereas stock versions cover a lot more and so the ARM arch is probably very small number of their users. Hence why I recommend that Linaro takes down their buggy compiler. Their 4.8.3 version should not be used *anywhere*, just the same as the stock 4.8 to 4.8.2 inclusive should also not be used anywhere on ARM either.

10 years, 8 months

2
1
0 0

[ACTIVITY] Week 41

by Charles Baylis

== Progress == Neon vld/vst [4/10] . submitted v2 of vldN_lane patch (respin of patches 1&2 only) . continued ML discussion about patches 3&4. Tried out jenkins/cbuild infrastructure [1/10] . hardest part was getting git.linaro.org/people to hold my test tree . https://wiki.linaro.org/Platform/Systems/GitServer#Creating_new_repositories . if it doesn't work, ask ITS to check you are in the git-users group . still need to find where the results go. bug 403/418 wrong line number on neon error messages [2/10] . experimented with a couple of ways to solve this bug 715 [2/10] . investigated and closed as only affects deprecated old ABI Misc [1/10] == Plan == Benchmark 2014.10 release Continue bug 403/418 work

10 years, 8 months

1
0
0 0

[ACTIVITY] 6 - 10 October 2014

by Will Newton

== Progress == * Further work on malloc single-thread optimizations (2/10, TCWG-436) - Still pending some resolution on direction from upstream * Upstream work (1/10, CARD-341) - Patch review - Applied binutils patch for missing AArch64 relocs * Further work on malloc app benchmark framework (2/10, TCWG-441) - Found a possible way to get memory statistics without hacks, should improve speed and reliability of the benchmark framework * Email, meetings, etc. (1/10) * Thursday and Friday annual leave (4/10) == Issues == * None == Plan == * Get malloc app benchmark framework into shape and committed * Figure out direction for malloc single thread optimization work -- Will Newton Toolchain Working Group, Linaro

10 years, 8 months

1
0
0 0

[ACTIVITY] 6th - 10th October

by Bernie Ogden

cbuild2 benchmarking - TCWG-360 [7/10] * Fixed/worked around some especially resilient bugs ** Mostly relate to running benchmarks through LAVA, which may be less important in the near future * Wrote a doc * Upstreamed some code that works about as I want it to Meetings/mail/etc [3/10] =Plan= cbuild2 benchmarking * Work through TODO list from connect * Tidy up behaviour on shutdown * Storage issues * (Maybe) persuade a LAVA Juno to work for benchmarking or configure spec Hopefully pick up something else

10 years, 8 months

1
0
0 0

[ACTIVITY] Week 41

by Yvan Roux

== Issues == * None. == Progress == * GCC 4.9 2014.10 (6/10) - Completed remaining backports. - Looked at some regression (1 backport reverted) * TCWG 59 : Improve libunwind AArch64 support (1/10) - Reviewed AArch64 patch. * Misc: (3/10) - Various meetings. == Plan == * FSF branch merge and 2014.10 release.

10 years, 8 months

1
0
0 0

[ACTIVITY] 6 October 2014 to 10 October 2014.

by Venkataramanan Kumar

= Progress == * Core mark benchmark and report for PGO and PGO + LTO (4/10) More profiling and collected numbers and reported. JIRA card TCWG-181 updated. Adding LTO gains in x86 and degrades in Aarch64 . * Addressed machine bring up issues, debugged and installed necessary packages for both x86 and Aarch64 (1/10) * PR 62308 - Analyzed RTL dumps. Looks to be similar issue solved in trunk. Git bisected and found the passing revision in trunk. posted my comments. waiting for feedback. (2/10) * Misc [3/10] Internal work, emails, AMD meetings and 1-1 with inline manger. 1-1 with Maxim, christophe and 1-1 with ryan Linaro status call == Plan == * Coremark benchmark and profiling for PGO and PGO + LTO. Investigate LTO degradation causes and report. * Investigate PR 63173 * Setup Cbuildv2 build in internal machine. == Issues == Experiencing Hardware connection issues and kernel instability issues with my local machines.

10 years, 8 months

1
0
0 0

[ACTIVITY] 6-10 October 2014

by Kugan

== Holiday == * Public Holiday (2/10) * Leave (4/10) == Progress == * Zero/sign extension elimination with widening types (4/10) - Started experimented with a pass for widening type. - Verified for one simple test-case. - Bootstrapping is failing and looking into it. == Plan == * Continue with Zero/sign extension pass.

10 years, 8 months

1
0
0 0

[ACTIVITY] Week 41

by Renato Golin

== Progress == * Automation Framework (CARD-1378 1/10) - Planning LAVA server for new TCWG gateway * Buildbots (TCWG-76 7/10) - Fixing Compiler-RT buildbot (from 69 to 4 failures) * Background (2/10) - Code review, meetings, discussions, etc. - Re-testing a change in inst combine that broke bots before - Reviewing CMake builder for Windows builds - Discussing clang-reformat on lld's codebase == Plan == * Continue fixing the Compiler-RT buildbot * Present 2 talks at Linux Plumbers

10 years, 8 months

1
0
0 0

[ACTIVITY] 6-10 October 2014

by Christophe Lyon

== Progress == * GCC trunk/4.9 cross-validation (CARD-647) (2/10) - trunk build for aarch64 reported to fail because libsanitizer requires an update. Pinged libsanitizers maintainers but got no answer so far. - posted testsuite patch to test if -shared is supported - managed to find how to force target-dependent -mword-relocations flags to compile testglue, without needing a testuite patch :-) * Validation (3/10) - compared cbuild2 schroot-test branch using (default) shared libs and forcing static libs Using static libs causes many unresolved and unsupported tests - compared using unix.exp and arm-linux.exp: the latter causes creates instability in the results * Neon intrinsics tests (2/10) - rebased on trunk, applied requested changes - the make-check parallelization support has changed mid-September, took some time to discover that my .exp harness was now incompatible. * Misc (3/10) - calls/meetings == Next == * GCC trunk/4.9 cross-validation - continue investigation of abi_check test * Neon intrinsic tests update, trying to take float16 types into account * cbuild2: - compare results + validation time of stable and schroot-test branches - look at backport-test script + logs

10 years, 8 months

1
0
0 0

[ACTIVITY] 29th September - 3rd October

by Bernie Ogden

cbuild2 benchmarking - TCWG-360 [7/10] * Cleaned up and upstreamed some code that works * Fixed a couple of issues raised by LAVA people ** No longer scraping the logs ** No longer assuming stable IP addresses lowlevellock.h comments - CARD-341 [1/10] * Respun based on Carlos' comments Meetings/mail/etc - [2/10] =Plan= cbuild2 benchmarking * Upstream code-with-fixes * Write a doc * Invite people to start using this thing ** Assuming that the storage questions get resolved * Work through list of tweaks Get up to speed on glibc vector math thread

10 years, 8 months

1
0
0 0

[ACTIVITY] 29 September - 3 October 2014

by Will Newton

== Progress == * Investigate a number of bugs in Linaro toolchain (2/10) - Submitted patches for cbuild build failure with eglibc and i686 - Investigated BZ #675, gdb baud rate issue. Should be fixed by switch to cbuild - AArch64 PIE support seems to be ok? * Submitted a patch to add all missing relocs from AArch64 ABI 1.0 to binutils (1/10) * Email, meetings, etc. (1/10) * More malloc single-thread optimizations (6/10, TCWG-436) - Patches submitted to the list == Issues == * None == Plan == * More atomics work * Tidy up and commit malloc app benchmarks * Out Thursday and Friday for a wedding -- Will Newton Toolchain Working Group, Linaro

10 years, 8 months

1
0
0 0

[ACTIVITY] Week 40

by Yvan Roux

== Issues == * None. == Progress == * GCC 4.9 2014.10 (6/10) - Tracked validation issues, Jenkins/Cbuild2 now fixed and usable. - Backported and validated ~30 revisions. - Commits in svn branch ongoing. * TCWG 59 : Improve libunwind AArch64 support (3/10) - Looked at upstream AArch64 patch review request. - Looked at testsuite failures * Misc: (1/10) - Various meetings. - AArch64 Libunwind upstream patch review. == Plan == * Finish backports commits in our FSF svn branch. * FSF branch merge. * Libunwind.

10 years, 8 months

1
0
0 0

[ACTIVITY] 29 September - 3 October 2014

by Kugan

== Progress == * LR register not used in leaf functions (TCWG-539) (1/10) Reviewed Jiong's changes. * bug #412 (2/10) - Seems to have been fixed but since there is not specific test-case except that it happens with spec2k gcc, need more work to be entirely sure. * AArch64 Spec2006 int regression (1/10) - Looked at bug databases and mailing list archive for more information * armv3 (bug #85 and bug #410) (2/10) - Looked at both the outstanding bug to find more information - proposed using -mno-lra for armv3 after discussion with the team * Misc (2/10) - Public holiday (2/10) - Annual Leave (2/10) == Plan == * zero/sign extension elimination with widening types == Holidays == * 06/10/2014 - Public holiday * 07/10/2014 and 07/10/2014 - Annual leave

10 years, 8 months

1
0
0 0

[Weekly] 29 SEPT - 3 OCT 2014

by Michael Collison

== This week == * TCWG-515 - Neon intrinsic testing part 1 (5/10) - Developed fix for vclz DejaGnu failure - Tested on ARM hardware * Linaro bugzilla 602 - gcc 4.7.3 compiler internal error while building hsail components (1/10) - Unable to reproduce with either Linaro 4.8 or 4.9 * Linaro Bugzilla 540 - Median of three has unneeded register moves (1/10) - Results of Triage indicate generated code has improved though still not optimal - No plans for further improvement * Misc. (1/10) - Completed ARM annual review paperwork * Out sick Friday, October 3rd (2/10) == Next week == - Full validation testing on vclz bug fix - Create patch for vclz bug fix and send to gcc-patches list - Resolve any blocking issues to patch for bugzilla 331

10 years, 8 months

1
0
0 0

[ACTIVITY] 29 September - 3 October 2014

by Venkataramanan Kumar

= Progress == * Core mark benchmark and report for PGO and PGO + LTO (2/10) Collected benchmark scores and report sent internally. Adding PGO benefits coremark. LTO seems to hurt. More runs and profiling next week. Tired few experiments with -funroll-all-loops and seems to benefit. * Misc [2/10] Internal meeting and 1-1 with Ryan and inline manger. Revisited and closed PR61442 Short week leave on 29 Sep, 2 and 3rd Oct (6/10). == Plan == * Coremark benchmark and profiling for PGO and PGO + LTO * Investigate PR 62308 * Setup Cbuildv2 build in internal machine.

10 years, 8 months

1
0
0 0

[Activity] Aug 28 - Oct 5

by Rob Savoye

== Progress == * Fixed test infrastructure bugs (TCWG 1378 - 8/10). - Installed Foundation Model on all Hetzner machines so aarch64 bare metal testing works. - Refactored all board support files to eliminate duplication to reduce maintainance headaches. Fixed ldflags so now getting good results. - Backport job is working good now. - Worked on Gerrit/Jenkins integration, with the goal of having the notifications work *after* the test and validation is done. - More work on optimizing SSH connections by reducing extraneous commands in the test framework. - Recreated stable branch from master now that results are much better. * Meetings and Misc (2/10) * Fixed National Park internal wireless network, getting access to much better bandwidth than the crappy Guest one. :-) == Plan == * Escape Yosemite, hard during a great weather window, and being the only person in my group with a job... * Continue fixing remote testing support, merge "boards" branch into master, then make it stable after more testing.

10 years, 8 months

1
0
0 0

[ACTIVITY] Week 40

by Charles Baylis

== Progress == Closed bug #405 (not a bug) NEON load/store . reworked patches not to do type-punning [9/10] . investigated alternative ways to solve poor code generation with array of vector types Started investigating NEON bugs 403, 418 [1/10] == Plan == NEON load/store - submit new patches, continue upstream discussion Try out validation infrastructure for my own patches

10 years, 9 months

1
0
0 0

[ACTIVITY] 29 September - 3 October 2014

by Christophe Lyon

== Progres == * GCC trunk/4.9 cross-validation (CARD-647) (3/10) - aarch64 address sanitizer tests currently all fail at execution under qemu because they try to reserve 50GB of memory. Tried to push the limits with no success so far. - working on fixing support for testcases generating a shared lib - newly introduced abi_check for aarch64 fails on my side, probable testsuite configuration problem. * Linaro branches - updated backports spreadsheet - reviewed backports prepared by Yvan * Validation (3/10) - manually running builds+validations to compare master and chroot branches, see the diffs between static and dynamic libs in terms of PASS/FAIL, .... * Neon intrinsics tests (1/10) - No need to comply to the GNU coding style since it's imported from and existing testsuite. - only minor changes requested - should help having the 1st subset committed soon * Misc (3/10) - calls/meetings - bugzilla admin etc..

10 years, 9 months

1
0
0 0

[ACTIVITY] Week 40

by Renato Golin

== Progress == * Automation Framework (CARD-1378 5/10) - Broken Chromebooks in the lab - Setting up AMD machine - Setting up Juno boards * Background (5/10) - Code review, meetings, discussions, etc. - Writing LPC presentations - Broken buildbots == Plan == * Spend less time fiddling with hardware... * Fix the Compiler-RT buildbot * FPU parser (PR20787) * .fpu in assembler (PR20757) * -mpfu in driver (PR20700)

10 years, 9 months

1
0
0 0

[PATCH 1/2] lib/make.sh: Add support for installing headers for i686 and x86_64

by Will Newton

--- lib/make.sh | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/lib/make.sh b/lib/make.sh index fb7137c..b917ece 100755 --- a/lib/make.sh +++ b/lib/make.sh @@ -460,8 +460,15 @@ make_install() local srcdir="`get_srcdir $1 ${2:+$2}`" if test `echo ${target} | grep -c aarch64` -gt 0; then dryrun "make ${make_opts} -C ${srcdir} headers_install ARCH=arm64 INSTALL_HDR_PATH=${sysroots}/usr" - else + elif test `echo ${target} | grep -c i.86` -gt 0; then + dryrun "make ${make_opts} -C ${srcdir} headers_install ARCH=i386 INSTALL_HDR_PATH=${sysroots}/usr" + elif test `echo ${target} | grep -c x86_64` -gt 0; then + dryrun "make ${make_opts} -C ${srcdir} headers_install ARCH=x86_64 INSTALL_HDR_PATH=${sysroots}/usr" + elif test `echo ${target} | grep -c arm` -gt 0; then dryrun "make ${make_opts} -C ${srcdir} headers_install ARCH=arm INSTALL_HDR_PATH=${sysroots}/usr" + else + warning "Unknown arch for make headers_install!" + return 1 fi if test $? != "0"; then warning "Make headers_install failed!" -- 1.9.3

10 years, 9 months

3
5
0 0

[ACTIVITY] 8th - 26th September

by Bernie Ogden

cbuild2 benchmarking - TCWG-360 [9/10] * Knocked off a lot of rough edges * Now working fairly robustly lowlevellock.h comments - CARD-341 [4/10] * Got a bit stuck trying to follow condvar locking * But wasn't really needed to describe the code in question LCA [10/10] LCA recovery day [2/10] Meetings/mail/etc [5/10] =Plan= cbuild2 benchmarking: * Push upstream for others to look at * Sort out storage story for benchmark sources and results * Try to get working on a Juno (in LAVA, therefore on OE) * Look at our Jenkins scripts with a view to figuring out how to hook in * Work through list of bits 'n' pieces to fix - + Don't scrape logs (bad for server) + Don't fail on network timeouts + Extra target control knobs - disable ASLR, set a nasty nice value, maybe hugepages + Set appropriate flags automatically for cross-builds

10 years, 9 months

1
0
0 0

[ACTIVITY] 22 - 26 September 2014

by Will Newton

== Progress == * Monday off to recover from Connect (2/10) * Catch up on email (1/10) * Upstream work (1/10, CARD-341) - Patch review * Investigate malloc single-thread optimizations (1/10, TCWG-436) - More exploratory work on atomics * Investigate binutils support for full range of AArch64 relocs (1/10) * Annual leave Thursday and Friday (4/10) == Issues == * None == Plan == * More work on atomics * Figure out how to make an LLVM cross compiler with gas/ld -- Will Newton Toolchain Working Group, Linaro

10 years, 9 months

1
0
0 0

[ACTIVITY] Week 39

by Yvan Roux

2 post-connect days off (4/10) == Issues == * Validation is in an "under construction" state. == Progress == * GCC 4.9 2014.10 (4/10) - Analysed validation issues with our cbuild2 branches. * Misc: (2/10) - Catch up with mails. - Various meetings. - AArch64 Libunwind upstream patch review. == Plan == * Catch up with backports * Audit validation failures

10 years, 9 months

1
0
0 0

[Weekly] 22-26 SEPT 2014

by Michael Collison

== This week == * TCWG-515 - Neon intrinsic testing part 1 (6/10) - developed reduced test case to demonstrated vclz DejaGnu failure - Created upstream bug (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63365) - Bug triage discovered issue occurs in copy propagation * Linaro Bugzilla 331 - [4.9 Regression] ICE in final_scan_insn, at final.c:2952 (aarch64-linux-gnu) (2/10) - Completed validation testing and sent to gcc-patches for trunk review * Linaro bugzilla 602 - gcc 4.7.3 compiler internal error while building hsail components (1/10) - Bug triage * Misc. (1/10) - 1:1 Meetings == Next week == - Identify solution for upstream bug 63365 - Triage bugzilla 602 - Resolve any blocking issues to patch for bugzilla 331

10 years, 9 months

1
0
0 0

[ACTIVITY] 22-26 Sept 2014

by Kugan

== Progress == * LR register not used in leaf functions (TCWG-539) (2/10) Posted the patch after regression testing https://gcc.gnu.org/ml/gcc-patches/2014-09/msg01833.html * AArch64 Spec2006 int regression (3/10) - After struggling to boot Juno, found the combination that works - Ran spec2006 int benchmarks to try reproduce - waiting for more information to continue * Launchpad bugs (LP1331112, LP1332640. LP1331126 and LP1320965) (3/10) - Set-up cbuild2 and spec2k on aarch64 board - ran aarch32 and aarch64 in aarch64 board with 09.2014 - Updated the bug entries with the results * Misc (2/10) - Connect recovery (2/10) == Plan == * 29/09/2014 - Public holiday * Get back to zero/sign extension with pass to promote operations

10 years, 9 months

1
0
0 0

[Activity] 22 - 26

by Venkataramanan Kumar

== Progress == * Connect recovery [6/10] Very short week short week travel back from connect 22nd - 23rd travel. 25th - sick leave. * Backport - Bug 676 - CSE did not optimize the redundant cmp instruction on aarch64 [2/10]. Checked the issue by building latest trunk, linaro branch and by adding the patch on top of linaro branch . Validated the code generated at -O2 and it seemed to be optimal and bug does not occur. Discussed with Christophe and decided to rebackport it along with 211881. It was reverted because of an libjava bug which is fixed in 211881. Used back flip to back port, git review was not automatically working. So manually amended by adding the change log for combined backport of revisions 209643 and 211881. * Misc [2/10] Prepared notes on LCU14 to AMD team. Examined spec benchmark in internal Aarch64 hardware for a support issue. Internal meeting and 1-1 with manager. == Plan == * Coremark benchmark and report for PGO and PGO + LTO * Get profiles on trunk for PGO and PGO + LTO * 29/9/2014 - Personal day off * 2/10/2014 - 3/10/2014- Dusserra Holidays Leave

10 years, 9 months

1
0
0 0

[ACTIVITY] Week 39

by Charles Baylis

== Progress == * Connect recovery [4/10] * NEON load/stores (TCWG-516 [5/10]) . initial review of my vldN_lane asm()->__builtin patches is promising . the other patches for other loads/stores are wrong. Have been investigating (with upstream) how much bigger the can of worms is. * Misc [1/10] . LCA15 travel . bug investigation (#405) == Plan == * more NEON load/store

10 years, 9 months

1
0
0 0

[ACTIVITY] 22-26 Sept 2014

by Christophe Lyon

Short week, 2 days holiday (4/10) == Progress == * GCC trunk/4.9 cross-validation (2/10) - reported a few new FAILs - trying to allocate time to fix new FAILs introduced in the 4.9 branch on devirt-28a.C, mostly because a testsuite configuration problem. - fixed reporting of email-driven validations * AArch64 libsanitizer - finally committed asan+ubsan support for AArch64! * Misc (4/10) * email catch-up * calls/meetings * updated backports speadsheet, backlog now > 75 * bugzilla management == Next == * GCC trunk/4.9 cross-validation: - actually reproduce+propose fixes for a couple of regressions recently observed * AArch64 thread sanitizer * Neon intrinsic tests * Analyze failures in Backport job in Jenkins * Analyze differences in validation results between using shared libs and static libs

10 years, 9 months

1
0
0 0

[ACTIVITY] Week 39

by Renato Golin

== Progress == * Two days holiday * Toolchain (CARD-862 2/6) - http://llvm.org/PR20700 (-Wa,-mfpu in IAS) WIP - http://llvm.org/PR20702 (vadd #imm, fix vbic) FIXED * Background (4/6) - Code review, meetings, discussions, etc. - Catching up with reviews & emails post-connect == Plan == * Continue -Wa,-mfpu implementation in IAS * Start implementing fpu stuff in assembler * Fix the Compiler-RT buildbot * Add libc++abi buildbot

10 years, 9 months

1
0
0 0

updated stable branch

by Rob Savoye

I just updated the stable branch to match master, which in my testing has been reliable and stable. I also changed the following Jenkins jobs to use the stable branch: Backport, BuildFarm, BinaryRelease, SourceRelease. Note that now any Jenkins job that runs tests and validates them using the tcwgweb.sh script, the build and test run may succeed, but if there are any regressions, the dot will be Red now instead of Green. This primarily effects the Backport and the Release jobs. - rob -

10 years, 9 months

2
1
0 0

updating stable branch today

by Rob Savoye

Unless anyone has a problem, I'm going to update the stable branch from master this afternoon. - rob -

10 years, 9 months

1
0
0 0

Re: what options should to compile aarch64 by gcc 4.9.

by Yvan Roux

Hi Sugar, the toolchain you need is the one with the aarch64-linux-gnu triplet. Regards, Yvan On 18 September 2014 08:05, Sugar <shugelinux(a)gmail.com> wrote: > Hi yvan, > I saw linaro have released > gcc-linaro-arm-linux-gnueabihf-4.9-2014.08_linux.tar.bz2. I have compiled > cortex-a53 by 'arm-linux-gnueabihf', but its binary is 'ELF 32-bit LSB > executable', not 'ELF 64-bit'. > Is it only compile to aarch32? If I want to compile aarch64, which > toolchains I should choose? Or what options should pass to compiler. > > Thanks.

10 years, 9 months

1
0
0 0

Toolchain for kernel 2.6.36

by Joel (Xi Zhou) Zhou

Hi all, I'm using ct-ng to rebuild Linaro toolchain (arm-linux-gnueabihf ) for Linux kernel 2.6.36. Ct-ng version: ct-ng-linaro-1.13.1-4.8-2014.01-01 There is a “FATAL: Kernel too old” message after mounting the rootfs. It turns out the default config using pre-built sysroot from Linaro website. After setting " CT_PREBUILT_SYSROOT=n" to build sysroot with lower kernel version, I get the following error: [EXTRA] Building final compiler [ERROR] /projects/broadcom-linux/joelz/opt/gcc-linaro-arm-linux-2.6-gnueabihf/arm-linux-gnueabihf/libc/usr/include/gnu/stubs.h:7:29: fatal error: gnu/stubs-soft.h: No such file or directory [ERROR] make[5]: *** [_muldi3.o] Error 1 [ERROR] make[4]: *** [multi-do] Error 1 I tried to put " -mfloat-abi=hard" as CFLAG in different place, still can't pass this error. If you have any idea how to fix it, please let me know. Thanks, Joel

10 years, 9 months

2
2
0 0

[ACTIVITY] 8-12 September 2014

by Christophe Lyon

== Progress == * GCC trunk/4.9 cross-validation (2/10) - noticed a couple of newly introduced failing tests in some corner cases - improved notification of selected commits to help fill the backports speadsheet * AArch64 libsanitizer - answered Marcus/Andrew after their feedback * Misc (conf calls, meetings, ....) 6/10 - usual 1/1 and team calls - Connect preparation - travelled on Friday == Next == * Connect LCU14

10 years, 9 months

1
0
0 0

[ACTIVITY] Week 37

by Renato Golin

== Progress == * Toolchain (CARD-862 6/10) - http://llvm.org/PR20529 (VFP unwind libcxxabi) - http://llvm.org/PR20700 (-Wa,-mfpu in IAS) - http://llvm.org/PR20702 (vadd #imm, fix vbic) * Buildbots (TCWG-76 1/10) - Three new ARMv7 buildbots with CMake are up - Another ARMv7 Benchmarking buildbot (tracking) * Background (3/10) - Code review, meetings, discussions, etc. - Connect preparations, taxi booking, etc == Plan == * Connect then... * Finish vadd, -mfpu * Start implementing fpu stuff in assembler * Fix the Compiler-RT buildbot * Work on LPC presentations

10 years, 9 months

1
0
0 0

[ACTIVITY] 8 - 12 September 2014

by Will Newton

== Progress == * More work on malloc app benchmark framework (1/10, TCWG-441) - Postgres still has an issue with SELinux on Fedora... * Email, meetings, etc. (1/10) * Upstream work (3/10, CARD-341) - Patch review - Investigate glibc testsuite build failures on ARM * Investigate malloc single-thread optimizations (4/10, TCWG-436) - Atomics changes look like they will only help on AArch64 - Some improvements can be made to atomic code in general on ARM and AArch64 - Still need to look at locking * Peparing and packing for Connect (1/10) == Issues == * Electric/gas meter replacement and broken refrigerator consumed some time == Plan == * Linaro Connect -- Will Newton Toolchain Working Group, Linaro

10 years, 9 months

1
0
0 0

[ANNOUNCE] Linaro GCC 4.9 2014.09 released

by Yvan Roux

The Linaro Toolchain Working Group (TCWG) is pleased to announce the 2014.09 release of the Linaro GCC 4.9 source package. Linaro GCC 4.9 2014.08 is the sixth Linaro GCC source package release. It is based on FSF GCC 4.9.2-pre+svn214896 and includes performance improvements and bug fixes. 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 enginering[2] releases. Interesting changes in this GCC source package release include * Updates to GCC 4.9.2-pre+svn214896 * Backport of [AArch32] TARGET_ATOMIC_ASSIGN_EXPAND_FENV hook * Backport of [AArch32] Enable arm target in ira-shrinkwrap-prep* testcases * Backport of [AArch32] fix check_effective_target_arm_nothumb * Backport of Do not convert cast + __builtin_round into __builtin_lround unless -fno-math-errno is used * Backport of [AArch64] Fix Thumb2 testsuite fallout * Backport of [AArch64_be] Fix vec_select hi/lo mask confusions. * Backport of [AArch64_be] Don't fold reduction intrinsics * Backport of [AArch64] Fix offset glitch in load reg pair pattern * Backport of [AArch64][2/2] Add constrain to address offset in storewb_pair/loadwb_pair insns * Backport of [AArch64] Improve TARGET_LEGITIMIZE_ADDRESS_P hook * Backport of [AArch64] Removed unused get_lane and dup_lane builtins. * Backport of [sched-deps] Generalise usage of macro fusion to work on any two insns * Backport of [doc] Document clrsb optab and fix some inconsistencies * Backport of [AArch64] Some aarch64-builtins.c cleanup. * Backport of Guard transformation to lrint by -fno-math-errno * Backport of [AArch32] Adjust clz, rbit and rev patterns for -mrestrict-it * Backport of [AArch32/AArch64] Add CRC32 scheduling information to Cortex-A53 and Cortex-A57 * Backport of [AArch64] Use REG_P and CONST_INT_P instead of GET_CODE + comparison * Backport of [AArch64] Prefer dup to zip for vec_perm_const; enable dup for bigendian; * Backport of [AArch32] TARGET_ATOMIC_ASSIGN_EXPAND_FENV hook * Backport of [AArch64] Use MOVN to generate 64-bit negative immediates where sensible * Backport of [AArch64] Delete f_sels, f_seld types, use fcsel instead * Backport of PR target/60606 target/61330 fix ICE * Backport of [AArch64] PR target/63190 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 Launchpad against "Linaro GCC project": http://bugs.launchpad.net/gcc-linaro/+filebug. * 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.

10 years, 9 months

1
1
0 0

Weird problem building the 2014.08 toolchain in i686-lucid

by Bernhard Rosenkränzer

Hi, I'm having some very odd problems building the 2014.08 toolchain respin -- in the cbuild1 i686-lucid env, building glibc fails with [ERROR] ../sysdeps/unix/sysv/linux/bits/sched.h:127:14: error: variably modified '__bits' at file scope [ERROR] ../sysdeps/unix/sysv/linux/bits/sched.h:127:14: error: variably modified '__bits' at file scope [ERROR] ../sysdeps/unix/sysv/linux/bits/sigset.h:29:23: error: variably modified '__val' at file scope [ERROR] ../sysdeps/unix/sysv/linux/bits/sigset.h:29:23: error: variably modified '__val' at file scope [ERROR] ../misc/sys/select.h:69:15: error: variably modified 'fds_bits' at file scope [ERROR] ../misc/sys/select.h:69:15: error: variably modified 'fds_bits' at file scope [ERROR] /cbuild/slaves/oorts/crosstool-ng/builds/aarch64_be-linux-gnu-linux/install/aarch64_be-linux-gnu/libc/usr/include/linux/posix_types.h:25:16: error: variably modified 'fds_bits' at file scope [ERROR] /cbuild/slaves/oorts/crosstool-ng/builds/aarch64_be-linux-gnu-linux/install/aarch64_be-linux-gnu/libc/usr/include/asm/sigcontext.h:33:2: error: requested alignment is not a positive power of 2 [ERROR] /cbuild/slaves/oorts/crosstool-ng/builds/aarch64_be-linux-gnu-linux/install/aarch64_be-linux-gnu/libc/usr/include/asm/sigcontext.h:53:2: error: unknown type name '__uint128_t' [ERROR] /cbuild/slaves/oorts/crosstool-ng/builds/aarch64_be-linux-gnu-linux/install/aarch64_be-linux-gnu/libc/usr/include/linux/posix_types.h:25:16: error: variably modified 'fds_bits' at file scope [ERROR] /cbuild/slaves/oorts/crosstool-ng/builds/aarch64_be-linux-gnu-linux/install/aarch64_be-linux-gnu/libc/usr/include/asm/sigcontext.h:33:2: error: requested alignment is not a positive power of 2 [ERROR] /cbuild/slaves/oorts/crosstool-ng/builds/aarch64_be-linux-gnu-linux/install/aarch64_be-linux-gnu/libc/usr/include/asm/sigcontext.h:53:2: error: unknown type name '__uint128_t' [ERROR] ../ports/sysdeps/unix/sysv/linux/aarch64/sys/user.h:32:3: error: unknown type name '__uint128_t' [ERROR] ../ports/sysdeps/unix/sysv/linux/aarch64/sys/user.h:32:3: error: unknown type name '__uint128_t' (Yes, the fix is to get rid of cbuild1 and more importantly the requirement for 32-bit builds in a prehistoric environment - it builds just fine on 64-bit present-day boxes... But I don't think we want to make that change in a respin). The "variably modified" errors remain even after hardcoding typedef struct { __cpu_mask __bits[16]; } cpu_set_t; instead of relying on __CPU_SETSIZE and __NCPUBITS, and the line where it complains about alignment not being a positive power of 2 actually hardcodes an alignment of 16. Have you run into those before? ttyl bero

10 years, 9 months

2
1
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain