Re: Linaro GCC vs Valgrind

This looks like a valgrind bug to me. I can reproduce the problem with this simple program, which shows the issue at any optimisation level. int main () { asm volatile ("" : : : "r4", "r5"); return 0; } [on my raspberry pi, with the system gcc] $ gcc test.c -mtune=cortex-a15 -marm $ valgrind .

Re: GNU GCC development plan and its interaction with Linaro

On 2 December 2015 at 14:15, Yvan Roux wrote: >> 1. What is the difference between experimental(gcc 6.0.0 stage 3) & gcc >> release branch (gcc 5.2.1)? > > trunk (actual gcc 6.0.0) is where everything goes, new features, new > optimizations, new targets, bugfixes, etc ... On release branches it >

Re: Building for armv6/ARM1136J-S using ABE

Since arm1136j-s does not support Thumb-2, you need to make sure that GCC is not configured with --with-mode=thumb. I don't think there is currently a way to achieve this on the abe command line at present. However, you can work around the problem by removing each occurrence of --with-mode=thumb f

[ACTIVITY] 24th - 28th August

Bug 1764/PR67280 C++ wrong code bug (no card yet) [9/10] Misc [1/10] ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ACTIVITY] 17th - 21st August

Holiday [2/10] Bug 1764/PR67280 C++ wrong code bug (no card yet) [4/10] Misc [4/10] ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ACTIVITY] 27-31 July

Holiday [2/10] Illness [2/10] TCWG-835 - Vector division [1/10] . patch review TCWG-867 - AArch64 post-idx addressing [4/10] . prototype patch works . vectorizer needs more work to exploit this Misc [1/10] ___ linaro-toolchain mailing list linaro-tool

[ACTIVITY] 13-17 July

Holiday [4/10] Benchmarking [3/10] TCWG-867 - AArch64 post-idx addressing [2/10] . prototype patch Misc [1/10] ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ACTIVITY] 20-24 July

Benchmarking [1/10] TCWG-775 NEON error messages [1/10] . AArch64 patch set approved . rebased/retested and applied TCWG-830/833/835 Vectorization project [5/10] . emails, calls, patch review TCWG-867 - AArch64 post-idx addressing [2/10] . debugging prototype patch Misc [1/10] _

[Activity] June 29 - July 3

Sick leave [2/10] (TCWG-775) NEON error messages [2/10] . validated patch, posted upstream (TCWG-831) vectorization/addressing modes [3/10] . reading/comparison of ARM vs AArch64 rtx_cost functions Misc [3/10] email etc ___ linaro-toolchain mailing lis

[ACTIVITY] 22-26 June

== Progress == (TCWG-831) post-indexed addressing [3/10] . vectorization project kick-off call . code browsing/reading to understand mailing list feedback about previous patch (TCWG-775) NEON error messages [6/10] . completed conversion of some ARM intrinsics to give same error messages as AArch6

[ACTIVITY] 15-19 June

== Progress == Sprint recovery [2/10] (TCWG-775) NEON intrinsics error messages [7/10] . familiarisation with differences between ARM and AArch64 NEON/SIMD backends . started porting error reporting changes to ARM NEON backend . pinged patch for AArch64 work Misc [1/10] == Plans == continue NE

[ACTIVITY] 25-29 May

== Progress == TCWG-775 NEON error messages (2/10) . wrote new patch for Aarch64 . tried to test it, but GCC testsuite stopped working on my laptop (random failures with "test for errors, tests randomly being marked UNSUPPORTED) Bank Holiday [2/10] Bug #1599 [1/10] . reproduced bug on Linaro GCC

Re: 502 connecting to abe.tcwglab.linaro.org

Hi Virendra, Thanks for the report. This has already been raised in our bugzilla at https://bugs.linaro.org/show_bug.cgi?id=1536 On 15 May 2015 at 06:08, Virendra Kumar Pathak wrote: > Hi, > > I tried on abe 'stable' branch and with below configuration build was > successful. > > ../abe/confi

[ACTIVITY] Week 14

== Progress == Holiday [6/10] (inc 1 bank holiday) Vectorization (TCWG-735) [2/10] . wrote some test cases Misc [2/10] Meetings, abe bugs ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lina

[ACTIVITY] Week 15

== Progress == Bank Holiday [2/10] Backports [2/10] . started and abandoned backport of 217440 due to unbackported dependent patch . FSF 4.9 branch is missing from our git mirror - this is still wasting time after 7 months Vectorization (TCWG-735) [3/10] Benchmarking [1/10] . started 2015.03 be

[ACTIVITY] Week 13

== Progress == qemu-system experiment [4/10] Tried to set up qemu-system for reliable simulated validation of tests which don't work under qemu-user. Mostly works, but there is arcane interaction between DejaGNU, gcc testsuite and board files which make it a bit flakey. Interesting experiment, but

[ACTIVITY] 9 - 13 March

== Progress == Off sick [4/10] Backporting [2/10] . unexpected conflicts and test failures meant that previous attempts were abandoned . will try again for 2015.04 Benchmarking [1/10] . one config failed, restarted in Jenkins . accessing Jenkins benchmarks still requires help from Bernie due to

[ACTIVITY] 2 - 6 March

== Progress == Benchmarking 2015.02 [2/10] . it turns out to be difficult to build previous releases with abe.sh (bz#776, bz#1307) . submitted patch to gerrit to improve abe.sh error handling . benchmarks started on Jenkins Backports [4/10] . investigating incorrect merge discovered in review . r

Re: Does gcc know about ldp

It is also planned to include this feature in Linaro GCC in the 2015.03 release. On 5 March 2015 at 09:23, Pinski, Andrew wrote: > It does but not in GCC 4.9. It was added for GCC 5. > > Thanks, > Andrew Pinski > > > From: linaro-toolchain-boun...@lists.l

[ACTIVITY] 23-27 Feb

== Progress == Bug triage [2/10] Bug 1199 analysis [4/10] reproduced, studied IRA dumps for a while, will have to report this upstream Backports + BackFLiP enhancement [3/10] Misc [1/10] meetings, git training presentation, mailing lists == Plans == benchmark 2015.02 release more bugs __

[ACTIVITY] 16-20 Feb

== Progress == Connect recovery [4/10] Looked for bugs to fix... [5/10] PR38674 - found to be duplicate, closed bug#1199 - cannot reproduce yet bug#1178 - accidental duplicated effort with Prathamesh Misc [1/10] ___ linaro-toolchain mailing list linar

[ACTIVITY] Week 5

== Progress == Benchmarking [6/10] Connect workshop prep [3/10] Misc [1/10] == Plans == more benchmarking... attempt Connect workshop dry run Fly to Connect ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.or

[ACTIVITY] week 4

== Progress == Benchmarking (3/10) . no results, scripts failed Connect workshop prep (4/10) Misc (1/10) Holiday (2/10) == Plan == Connect workshop prep . trial run with willing volunteer Benchmarking . talk to Bernie, try again ___ linaro-toolcha

[ACTIVITY] Week 3

== Progress == Illness [5/10] Aarch64 NEON error messages [2/10] Benchmarking [2/10] Misc [1/10] slides for connect == Plan == Benchmarking... ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listi

[ACTIVITY] 1-5 December

== Progress == Bug#403/#418/PR63870 [7/10] . Prepared patches for vldN_lane/vstN_lane . reviewed related patches on list . code changes are ready, but reveal errors in the testsuite Misc [3/10] . mailing llists . meetings . some help with lab config with Renato __

[ACTIVITY] 24-28 November

== Progress == Holiday [1/10] Investigated bug #928 [4/10] . turns out to be invalid implementation of memset in old linux kernels . raises a question - do we want to provide support for users of old Linux kernels on new compilers? We could spend a long time rehashing work the kernel community ha

[Activity] Week 46

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

[ACTIVITY] 3-7 November

== Progress == Bug 404 [5/10] Bugs 403/418 [2/10] Misc [3/10] . office move . review ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ACTIVITY] Week 43

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

[ACTIVITY] Week 42

== 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 ___ linaro-toolchain mailing list linaro-toolchain@lists.

[ACTIVITY] Week 41

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

[ACTIVITY] Week 40

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

[ACTIVITY] Week 39

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

Re: [ACTIVITY] Week 30

On 28 July 2014 14:45, Kugan wrote: > It could be the kernel version we use in lab. AFAIK, Charles had some > luck profiling with perf on newer kernel. I am not sure about the > version though. I have seen working performance counters on 3.15-rc8. The versions of the kernel we have on our aarch64

[ACTIVITY] June 23 - 27

* Analysis of PR61411 (CARD-341) [2/10] * Attempted to analyse VP8 decode performance on Aarch64 vs Aarch32 (TCWG-?) [6/10] . took a while to find compatible libvpx source and compilers :( . can't find a good way to profile on Aarch64, perf is broken, gprof results look implausible * Misc [2/10]

[ACTIVITY] 16 - 20 June

* Linaro bugzilla #24 - [6/10] * investigating cause of ICE in Linaro 4.9 * PR61411 [1/10] * Committed patches for division (TCWG-???) and Neon address mode (TCWG-430) [1/10] * Admin [1/10] * Holiday [1/10] ___ linaro-toolchain mailing list linaro

[ACTIVITY] 26-30 May

Progress Bank holiday [2/10] Retested VLD post-indexing patch, held up by trunk breakage TCWG-430 [2/10] libvpx VP9 performance investigation TCWG-429 [4/10] libvpx aarch64 ICE investigation [2/10] ___ linaro-toolchain mailing list linaro-toolchain@

[Activity] 2 - 6 June

Progress: Investigation following review feedback of VLD post-indexing patch TCWG-430 [8/10] libvpx VP9 performance investigation TCWG-429 [2/10] ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listin

[ACTIVITY] May 12-16

== Progress: == Holiday [2/10] Rewrite of division optimisation changes following review - TCWG293 [8/10] == Plan == Mostly on holiday this week. I may be working sporadically ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http:/

[ACTIVITY] 28 April - 2 May

== Progress == Holiday [3/10] Post-indexed addressing for NEON on Aarch64 - TCWG-430 [3/10] * needs much more work than for ARM Revisited apparent NEON scheduling problem in libvpx - TCWG-429 [2/10] * it transpires that this was an incorrect analysis * the assembler code didn't conform to the AB

[ACTIVITY] 21-25 April

== Progress == Bank holiday [2/10] Investigated using D01 board [1/10] Retested and pinged division patch - TCWG-293 [2/10] Added post-index addressing to NEON memory access for ARM -TCWG-430 [5/10] * wrote patch * makes useful improvement to libvpx performance

[ACTIVITY] 7-11 April & 14-18 April

=== Previous === libvpx NEON intrinsics investigation [TCWG-429 14/10] . if interested, you can read the report in card 429: https://cards.linaro.org/browse/TCWG-429?focusedCommentId=22247 tested division optimisation patches against current trunk and pinged on list [2/10] good friday bank hol

[ACTIVITY] 31 March - 4 April 2014

=== Progress === LP1296601 (ICE in push_minipool_fix) [5/10] * completed a prototype fix * submitted RFC patch to gcc-patches * still awaiting review PR60609 (Error: value of 256 too large for field of 1 bytes) [3/10] * implemented fix and posted to gcc-patches * approved, subject to further test

[Activity] 17-21 March 2014

Last week * one day off [2/10] * NEON scheduling investigation - TCWG-135 [3/10] . investigated scheduler register pressure heuristics . call with Maxim about scheduling algorithm . still more investigation required * NEON intrinsics vs assembler libvpx performance difference investigation [5/10] .

Re: Trouble executing ARM code on linaro toolchain

Hi On 6 March 2014 14:22, Vishwanath C wrote: > We are using Linaro 13.03 > toolchain(gcc-linaro-arm-linux-gnueabihf-4.7-2013.03-20130313_linux We are > trying to execute a simple test code to check whether ARM assembly code > executes on board or not. Execution is on Arndale Board. Every time We

[ACTIVITY] Week 50

== Progress == TCWG-293 (9/10) - wrote and tested 64bit division code - it seems to work - still need to do performance testing TCWG-347 Fix PR59142 (1/10) - split into series of 3 patches - patch almost ready, was held up by non-availability of the lab - need to bootstrap on Thumb-1 to prove

[Activity] Week 39

Progress . worked on cleaning up arm config in gcc (TCWG-201) . not really convinced I have a way to properly test the result . a bit of bug triage . a bit more on the 4.7 segfault bug (lp1215925) Plans . ping the arm*gnueabihf testsuite patch . finish the config clean up . revisit 4.7 segfault,

[ACTIVITY] Week 32

Last week * tried cbuildv2 and sent Rob some bug fixes, bug reports, and feature requests * ported previous testsuite fixes to trunk This week * send patch to gcc-patches * find the next thing to fix Issues * need to take desktop PC back to supplier to fix CPU overheating ___

[ACTIVITY] Week 31

Last week * Wrote up notes on gcc cross-compiler building (WIP: https://wiki.linaro.org/WorkingGroups/ToolChain/BuildingGNUToolchains) * started looking at gcc test suite This week * produce at least one fix for a gcc testsuite test problem * book LCU13 * with luck, receive new laptop

[ACTIVITY] Week 30

== Progress == * Induction and set up work environment * Started investigating how to build gcc cross compilers, so that it can be documented clearly [TCWG-190 ] * I can build a working arm-none-linux-gnueabi crosscompiler, and understand each of the steps i