- linaro-toolchain - lists.linaro.org

[ACTIVITY] 30 May-3 June 2016

by Christophe Lyon

== Progress == * Validation - trying to improve cleanup job such that they skip offline nodes - reviews * Backports - successful backport for our gcc-6 branch * GCC - regressions reports on trunk - preparing removal of neon-testgen.ml * Misc (conf-calls, meetings, emails, ....) == Next == * Validation - prepare switch to docker for buildfarm job - cleanup * Backports * GCC - trunk monitoring - more on AdvSIMD intrinsics

9 years, 1 month

1
0
0 0

Re: [lld] r271569 - Start adding tlsdesc support for aarch64.

by Renato Golin

On 2 June 2016 at 23:22, Rafael Espíndola <rafael.espindola(a)gmail.com> wrote: > Because the patch includes way too much and doesn't explain what it is doing. So let me get this straight: someone publishes a patch, you don't like it, you do some private investigations and commit whatever you want without even notifying the original authors? I don't know how you work at your company, but this is not how open source development works. This is not the first time either that you step over people's toes with your "design decisions" that you don't share with anyone. Last year, Adhemerval has worked for three months to get the LLD AArch64 back-end working and out of the blue, no warning, the whole back-end was yanked. It doesn't matter if it was the right decision or not in the long term, we don't just yank things, especially not before some deliberation on the list. See how long is taking for the new pass manager to be enabled, or FastIsel or the new Selection, or the new register allocators, etc. That's not how open source works and I assumed you knew that. > That is a general problem with aarch64, the documentation is missing > and comments have to make due. I had a lot of work to rewrite the > original aarch64 patches to be in line with the rest of lld and I > didn't want to have to do the same for tls. You shouldn't be rewriting *any* patch, but asking the original authors to do that themselves. There is a pattern that I'm seeing and that's that *you* refuse or dismiss more patches than most other people. There are many of your comments on reviews that are just personal, and then you step over people's toes and commits yourself. This does not scale. But more importantly, it puts into doubt the validity of the tool you're so hardly defending. You see, 3 years ago, I was asked to choose between MCLinker and LLD. MCLinker was a linker for all purposes, but Chris Lattner convinced me that LLD is the LLVM linker, and we should be focusing all efforts there. It goes against the commercial interests of Linaro members to choose such a premature technology, and it did put them back years of development, because MCLinker was very close to ready, and MediaTek, despite what people said, was very willing to accept our help. But in the interest of the community, and the open source nature of my work, I have decided to pursue LLD and managed to convince Linaro to put two people working on it. But now, I'm re-evaluating all my strategy, and sincerely, I do not trust the LLD community anymore. > The delay was because of the above mentioned issues. I wanted to make > sure there was a solid foundation. Some patches are quick to review, others take 6 months. If you work in open source you have *got* to understand that. If you're not willing to take that cost, than please, refrain from working open source. > Sorry, no. I understand your position, but you have to understand mine. I therefore call into question your ability to care about such an important project of the LLVM community. I sincerely believe that your actions are harming the project, and the people trying to help. I appreciate the value of your contribution, I really do, but if you don't change your way to handle open source contributions, LLD will, whether you like it or not, become irrelevant and be replaced. Such is the nature of open source. cheers, --renato

9 years, 1 month

2
2
0 0

Re: [lld] r271569 - Start adding tlsdesc support for aarch64.

by Renato Golin

On 2 June 2016 at 20:49, Rafael Espindola via llvm-commits <llvm-commits(a)lists.llvm.org> wrote: > Author: rafael > Date: Thu Jun 2 14:49:53 2016 > New Revision: 271569 > > URL: http://llvm.org/viewvc/llvm-project?rev=271569&view=rev > Log: > Start adding tlsdesc support for aarch64. > > This is mostly extracted from http://reviews.llvm.org/D18960. Rafael, Why commit part of Adhemerval's patch without reviewing his request? This is a really serious breach of community trust. Not only we're waiting for reviews on the TLS set of patches and having to rebase every two weeks, but now you implemented in a way that wasn't discussed on the review, didn't mention authorship, nor asked Adhemerval for any input. If you had technical input on his patch, you should have done on the review. If you wanted him to split in smaller patches, you should have asked on the review and let *him* do it. Even if you were the code owner (which you're not), it would still be a *serious* breach of trust and respect. I hereby respectfully request that you revert your patch and let Adhemerval finish the work that he started in the way that we normally do in the LLVM community. regards, --renato

9 years, 1 month

1
0
0 0

[ACTIVITY] 23 - 27 May 2016

by Yao Qi

* Off on Friday [2/10] # Progress # * TCWG-518, V1 got reviewed, and working on V2. Two existing bugs in GDBserver are found, and fixed. Testing them... [4/10] * Upstream patches review, all of them are about GDB python. [2/10] * Respond to Jim Wilson's question on AIX GDB build failure caused by his binutils patch for AArch64. Confirm that GDB build fail after his patch. [1/10] * Misc, [1/10] # Plan # * Bank holiday on Monday, * TCWG-518, get V2 ready for review, * Ping TCWG-561 and TCWG-547, -- Yao

9 years, 1 month

1
0
0 0

[ACTIVITY] 23 - 27 May 2016

by Omair Javaid

=== This Week === Resolved TCWG-231 (LLDB bring up and bug fixing on HiKey 96Board) [TCWG-231] [1/10] -- Ran tests on AArch64 LLDB tests on HiKey and compared with Nexus 9 test results. -- Less than 1% difference in test results and good pass rate found. LLDB ARM: Bug fixes, integration and testing on various ARM platforms [TCWG-228] [2/10] -- Progressed towards resolution. -- Prepared close out setting up RaspberryPi2, RaspberryPi3, Hikey and Chromebook as testers. -- Compiled armhf test results. LLDB Chromebook Test Stability [TCWG-563] [2/10] -- Some further investigation on llvm-chrome-06 test failures. -- Marked and committed some xfails and reported relevant bugs if not already logged. Support for watchpoint un-alligned watchpoint addresses on LLDB AArch64 [TCWG-367] [1/10] -- Debugging of watchpoint handling code and tried out instruction decding. LLDB buildbot updates and maintenance [TCWG-241] [2/10] -- Improved tester script to initiate lldb-server inside a chroot. -- Monitored buildslave stability and Miscellaneous [2/10] -- Meetings, emails, discussions etc. -- Migrated laptop to Ubuntu 16.04 === Next Week === LLDB Chromebook Test Stability [TCWG-563] -- Final words on watchpoint issue on llvm-chrome-06 -- Submit updated makefile.rulez for LLDB tests. -- Report remaining bugs and commit xfails upstream. Support for watchpoint un-alligned watchpoint addresses on LLDB AArch64 [TCWG-367] -- Implement instruction decoding for watchpoint hit detection. A look into kernel code used by Nexus android devices failing watchpoint support [TCWG-622] Miscellaneous -- Out of office on Tuesday 31st 2016 for visa documents preparation.

9 years, 1 month

1
0
0 0

[ACTIVITY] Week 21

by Yvan Roux

* ! day off (2/10) == Progress == o Extended validation (2/10) - Benchmarking comparison script on-going - Reproduced armhf schroot slowness on AArch64 Debian Jessie No issues when using Ubuntu (Trusty and Xenial). o Upstream GCC (4/10) - Started ARMv8.1 libatomic support (environment setup, code understanding, ifunc support analysis) o Misc (2/10) * Various meetings and discussions. == Plan == o Continue libatomic work

9 years, 1 month

1
0
0 0

[ACTIVITY] 23 - 27 May 2016

by Prathamesh Kulkarni

== This Week == * TCWG-72 (6/10) - Patch iterations based on Richard's suggestions - Reworked most of convert_to_divmod() - Fixing regressions with the patch and added test-cases. - ICE with -m32 on x86_64 for DImode division/mod: https://gcc.gnu.org/ml/gcc-patches/2016-05/msg02302.html * LTO (2/10) a) TCWG-548 (1/10) - Benchmarking jobs submitted twice and failed. b) TCWG-535 (1/10) - Figured out why ICE happens with my patch. * TCWG-319 (1/10) - Validated patch and posted upstream. * Misc (1/10) - Meetings == Next Week == - TCWG-72: Try to workaround issue with -m32 - TCWG-548: start relooking at section anchors. - TCWG-535: Post patch upstream.

9 years, 1 month

1
0
0 0

[ACTIVITY] 23-27 May 2016

by kugan

== Progress == PR71252 - ICE in rewrite_expr_tree - Tried various options to fix this and settled on an implementation - Patches sent for upstream review - tested with cpu2006 too - One patch approved PR66726 - Convert expr - Newlib test case is failing due to mi compiled lib - Trying to reduce test case == Plan == Follow upon remaining upstream patches IPA VRP

9 years, 1 month

1
0
0 0

[ACTIVITY] 23-27 May 2016

by Peter Smith

== Progress == * LLD Port: - Got hello world running. -- Needed a horrible hack to make lld output PLT and GOT entries for unresolved weak references with default visibility. - Wrote up in Jira the major areas of work that would be needed for a useful port. - Started putting in changes cleanly and writing tests for them. - Currently hitting a few problems with llvm-mc. I can't generate the relocations I need to test the linker. The hello world test case used mainly GCC library objects. -- Most serious is not emitting R_ARM_BASE_PREL for .word _GLOBAL_OFFSET_TABLE - (label+8) == Plan == * On holiday Monday and Tuesday * LLVM MC See how easy it would be to add missing features to llvm-mc as it would allow me to write more tests. * LLD Complete the test cases for the code I've added. Take stock of where the lld port is and decide where to go from there. Options are: - Send an RFC upstream with what I have. It is not sufficient to run hello world but should be relatively uncontroversial. - Cleanly implement the emit the unresolved weak references in the PLT and GOT so hello world will work out of the box on ARM. - Keep going until I've got Thumb2 support so I don't have to use ARM only static libraries to make hello world working. There is obviously a trade off between having a useful linker and the patch size getting out of hand.

9 years, 1 month

1
0
0 0

[ACTIVITY] 23-27 May 2016

by Diana Picus

== Progress== * Remove exit-on-error flag from CodeGen tests [TCWG-604] [5/10] - This is a follow-up of TCWG-592: when changing the diag handler, some of the tests started to fail, so we had to add an exit-on-error flag to preserve the old behaviour until we can fix the tests. - Last week's patch fixing the MIR tests (PR27770) - still in upstream review - Last week's patch fixing an AMDGPU test (PR27762) - committed upstream - Last week's patch fixing a BPF test (PR27766) - committed upstream - Submitted another patch fixing a BPF test (PR27767) - committed upstream - Submitted another patch fixing two other BPF tests (PR27768/9) - in upstream review - Investigating one of the AMDGPU tests (PR27761) * Use git worktree in llvm helper scripts [TCWG-587] [4/10] - Started a RFC and a wiki page about the new workflow [1] - People seem to be in favour of it, but there are still some TODOs left before we can merge * Misc [1/10] - Meetings, buildbots == Plan == * Remove exit-on-error flag from CodeGen tests [TCWG-604] - Submit a patch for the AMDGPU test (PR27761) - More investigations on the ARM test (PR27765) * Use git worktree in llvm helper scripts [TCWG-587] - Finish the final touches and have a proper review [1] https://collaborate.linaro.org/display/LLVM/Git+Worktree+Proposal

9 years, 1 month

1
0
0 0

[ACTIVITY] 23-27 May 2016

by Christophe Lyon

== Progress == * Validation - cleanup - Fixed regressions in abe (gcc_update, make install, gdb timestamps) - updated abe stable branch (now matches master) - various Jenkins jobs updates, prepared support for gcc-6 based toolchains - compared results of armv8l vs arm toolchains: few, expected differences due to different default tuning * GCC - regressions reports on trunk * Misc (conf-calls, meetings, emails, ....) == Next == * Validation - actually update the Backport job - prepare switch to docker for buildfarm job - cleanup * Backports * GCC - trunk monitoring - more on AdvSIMD intrinsics

9 years, 1 month

1
0
0 0

Re: toolchain fetch issues

by Gujulan Elango, Hari Prasath (H.)

Sorry for hitting the wrong mailing list. OK I will check with HTTP instead of HTTPS. Thanks for your time & help. On May 25, 2016 11:02 PM, Jim Wilson <jim.wilson(a)linaro.org> wrote: On Wed, May 25, 2016 at 8:09 AM, Gujulan Elango, Hari Prasath (H.) <hgujulan(a)visteon.com> wrote: > I enabled the -v option of wget and I am able to see the download starts and > fails randomly after progressing to some extent i.e. 10% or 27%. The > connection is reset by peer and wget exits. I tried increasing the timeout > option of wget as well. This is some kind of networking or web server problem. We only know how to fix compiler problems here on the linaro-toolchain list. I did confirm that I can download the file OK, both via wget and via chrome.. I noticed that the https support on releases.linaro.org is not working, and I had to use http instead, but it isn't clear if that is related to your problem. Jim

9 years, 1 month

1
0
0 0

toolchain fetch issues

by Gujulan Elango, Hari Prasath (H.)

Hello, We have cloned the meta-linaro layer and when we build,we are facing some issues when the do_fetch() task is executing for the gcc-source-linaro-5.1 package. I enabled the -v option of wget and I am able to see the download starts and fails randomly after progressing to some extent i.e. 10% or 27%. The connection is reset by peer and wget exits. I tried increasing the timeout option of wget as well. Any idea what's wrong. Find attached the log of the error. Thanks & Regards, Hari Prasath

9 years, 1 month

2
1
0 0

missing gold --be8 support

by Jim Wilson

Cisco is trying to use clang/lto on big-endian arm, which apparently requires gold, and gold does not support the --be8 option which is required for ARMv7 big-endian support. Does anyone here care about this? Umesh Kalappa asked about this on the binutils mailing list https://sourceware.org/ml/binutils/2016-05/msg00209.html and discovered that it is a known bug reported 5 years ago https://sourceware.org/bugzilla/show_bug.cgi?id=13213 Jim

9 years, 1 month

3
5
0 0

[ACTIVITY] Week 20

by Yvan Roux

== Progress == o Extended validation (7/10) * Investigate GDB instabilities: - branch tracing issue are due to builder feature support - Our 2 old builders, which don't support it, removed from x86 validation pool * Benchmarking: - Looked at Lava instance API and lava-tool usage and prerequisite - Implementing comparison script o Misc (3/10) * Various meetings and discussions. == Plan == o Continue on validation/benchmarking o Catch up with upstream work.

9 years, 1 month

1
0
0 0

[ACTIVITY] 16 - 20 May 2016

by Omair Javaid

=== This Week === Support for watchpoint un-alligned watchpoint addresses on LLDB AArch64 [TCWG-367] [3/10] -- Made changes to NativeRegisterContext_arm64 to support multiple watchpoint slot for a single watch address. -- Enabled unaligned watchpoints and experimented with resulting false positives. LLDB Chromebook Test Stability [TCWG-563] [3/10] -- Migrated local builder to Ubuntu 16.04 xenial -- Ran LLDB testsuite with GCC 5.x.x on chromebook, raspberryPI2 -- Updated LLDB testsuite makefile.rulez to use correct cross AR and OBJCOPY LLDB buildbot updates and maintenance [TCWG-241] [2/10] -- Investigation of LLDB buildbot slave failure -- Implemented stale log deletion mechanism by making sure we keep only 10 most recent logs. LLDB upstream collaboration and Arm/AArch64 Linux port maintenance [1/10] -- Verify patches under review -- Analyzed TestTopLevelExprs on LLDB arm failure and committed xfail. Miscellaneous [1/10] -- Meetings, emails, discussions etc. -- Travel bookings for connect and TCWG sprint. === Next Week === Close out TCWG-231 (LLDB bring up and bug fixing on HiKey 96Board) -- Run and comparison of AArch64 LLDB test results vs hikey showing less than 5% difference. Close out LLDB Chromebook Test Stability [TCWG-563] -- Make sure there are no failures for which we dont know the underlying reason. -- Report remaining bugs and commit xfails upstream. Support for watchpoint un-alligned watchpoint addresses on LLDB AArch64 [TCWG-367] -- Further testing of false positive results due to allowing un-alligned watch-points. LLDB buildbot updates and maintenance [TCWG-241] -- Figure out difference of test results between local and remote chromebooks. -- Figure out a way to hide unused test slots by buildbot factory. Miscellaneous -- Migrate laptop to ubuntu 16.04 in hope of better driver support. -- Portugal visa and travel booking

9 years, 1 month

1
0
0 0

[ACTIVITY] 16=20 May 2016

by Christophe Lyon

== Progress == * Validation - cleanup - reviews - asserting ABE master vs stable results - stopped investigation on a huge number of unexpected regressions, maybe caused by builders crashes - created a Jenkins job able to detect the base GCC branch, in order to select the right libc/binutils version - found why ABE master showed regressions with the _Pragma3 GCC test. Fix under review. - investigating recent, numerous build failures * Backports - updated backport to fix bug #2185 after Kugan analysis - drafted a script to parse the spreadsheet and generate the backflip commands as appropriate * GCC - reported a couple of regressions on trunk - Neon intrinsics tests update: committed. We are now ready to remove neon-testgen.ml == Next == * Validation - cleanup - armv8l vs arm - ABE master vs stable * GCC - trunk monitoring - more on AdvSIMD intrinsics

9 years, 1 month

1
0
0 0

[ACTIVITY] 16 - 20 May 2016

by Kugan Vivekanandarajah

== Progress == PR40921 -missed optimization: x + (-y * z * z) => x - y * z * z - Patch committed PR63586 - x+x+x+x -> 4*x in gimple - Patch committed - There were couple of fallouts PR71179 - ICE fold_convert_loc, at fold-const.c:2360 - Patch committed PR71170 - ICE in rewrite_expr_tree, at tree-ssa-reassoc.c:3898 - Tried various options to fix this and settled on an implementation - Patch sent for upstream review == Plan == Follow upon remaining upstream patches IPA VRP

9 years, 1 month

1
0
0 0

[ACTIVITY] 16-20 March 2016

by Prathamesh Kulkarni

== This Week == * TCWG-528 (2/10) - Addressed comments from Richard and committed upstream (r236502, r236503) * TCWG-72 (5/10) - Updated patch and fixed regressions caused due to patch. * TCWG-319 (1/10) - Found why big endian vectorizer was not vectorizing the test-case with -O2. * Holiday (2/10) == Next Week == - TCWG-319: Post patch upstream and get it committed. - TCWG-72: Post patch upstream and hopefully get it committed this week. - TCWG-548: Start re-looking at section anchors.

9 years, 1 month

1
0
0 0

[ACTIVITY] 16 - 20 May 2016

by Peter Smith

=== Progress === TCWG-591 MOVW incorrectly allowed on ARM v5 committed upstream TCWG-595 LLD port to ARM architecture I am getting close to being able to run hello world built with lld. I'm converging 1 bug at a time. - The PLT handling code is working and the loader can execute the image and starts the .init function. - Currently failing in the weak call to __gmon_start__. At present lld is removing undefined weak references from executables instead of passing them on for the dynamic loader to resolve. This may not be necessary on x86 but it is necessary on ARM. -- Just finished a hack that should make this work, although it will need some tidying up. === Plan === Get hello world working and then take stock of what I've learned and come up with a plan in Jira for what needs to be done.

9 years, 1 month

1
0
0 0

[ACTIVITY] 16-20 May 2016

by Diana Picus

== Progress == * Add a diag handler for llc so it doesn't exit on the first error it finds [TCWG-592] [1/10] - Fixed and rebased the patch, it has been committed upstream * Inline assembly constraints support for ARM [TCWG-560] [1/10] - Rebased the patch, it has been committed upstream * Remove exit-on-error flag from CodeGen tests [TCWG-604] [4/10] - This is a follow-up of TCWG-592: when changing the diag handler, some of the tests started to fail, so we had to add an exit-on-error flag to preserve the old behaviour until we can fix the tests. - Submitted a patch fixing the MIR tests (PR27770) - in upstream review - Submitted a patch fixing an AMDGPU test (PR27762) - in upstream review - Submitted a patch fixing a BPF test (PR27766) - in upstream review - Investigated the ARM test (PR27765) * Use git worktree in llvm helper scripts [TCWG-587] [3/10] - Working on a prototype * Misc [1/10] - Meetings, buildbots, IRC issues - Got LLVM commit access, yay! == Plan == * Remove exit-on-error flag from CodeGen tests [TCWG-604] - Fix the remaining ARM, BPF and AMDGPU tests (unfortunately the ARM test seems a bit more involved, so I might pick out the others first just to get them out of the way) * Use git worktree in llvm helper scripts [TCWG-587] - Continue prototyping, start a RFC on it next week

9 years, 1 month

1
0
0 0

[ACTIVITY] 16 - 20 May 2016

by Yao Qi

# Progress # * TCWG-518, [6/10] fix all bugs, and post them upstreams for review! * PR 19998, write a patch to fix it. [2/10] * Some discussions on unstable GDB test results in validation tests. [1/10] * Meetings [1/10] # Plan # * Respond comments to my patches, * TCWG-333, think about the right fix. -- Yao

9 years, 1 month

1
0
0 0

Re: Issues with accessing TLS of shared object

by Bill Fischofer

This may be a better question for the linaro tools group. +cc their list for the general question of conventions surrounding how shared library objects identify and access thread-local storage that they need as part of calling threads. On Tue, May 17, 2016 at 11:06 AM, Nikhil Agarwal <nikhil.agarwal(a)linaro.org> wrote: > Hi All, > > I am trying to write a shared library object over ODP. Our ODP library has > some per thread variables. When my application invokes an API of shared > object which accesses per thread variable it gives segmentation fault. > > My concern is that when a shared object is loaded dynamically, how memory > is assigned to thread specific variables defined inside shared objects. > AFAIK we need to compile it with -ftls-model=global-dynamic, which is > enabled by default when compiled with -fPIC flag, and library loader > takes care for these issues. > > I am not an expert in this area, please help me in getting to some > suitable reference pointers or some steps I might have missed. > > Thanks in advance > > Nikhil >

9 years, 1 month

3
2
0 0

[ACTIVITY] 09 - 13 May 2016

by Omair Javaid

=== This Week === Enable LLDB testsuite to show zero failures on Hikey 96 Board (AArch64 Linux) [TCWG-231] [4/10] -- Ran multiple builds and testsuite runs to figure out latency issues. -- Investigated remaining failures and submitted appropriate bugzilla bugs. -- Committed xfails upstream. Support for watchpoint un-alligned watchpoint addresses on LLDB AArch64 [TCWG-367] [1/10] -- Some investigation on possible solutions and frequently encountered scenarios. LLDB Chromebook Test Stability [TCWG-563] [3/10] -- Investigation of noreturn unwinding test failure -- Investigation of step over load library call failure -- Investigation of other failures and commit xfails for reported issues. Miscellaneous [2/10] -- Meetings, emails, discussions etc. -- Portugal visa information gathering === Next Week === Support for watchpoint un-alligned watchpoint addresses on LLDB AArch64 [TCWG-367] -- Add code changes required to manage a watchpoint with multiple hardware watchpoint resources. LLDB Chromebook Test Stability [TCWG-563] -- Fix noreturn unwinding test failure and report relevent bug. -- Fix step over load library call failure or report relevent bug. Miscellaneous -- Portugal visa application documents preparation.

9 years, 2 months

1
0
0 0

[ACTIVITY] 9-13 May 2016

by Christophe Lyon

== Progress == * Validation - cleanup - reviews - looked a bit a using docker from Jenkins - investigating how to select toolchain components versions depending on the gcc version * GCC - Sent Neon intrinsics tests patches. - trunk timeouts: caused by the libcilkrts merge, which has a bug on arm. Disabled cilkplus to avoid too much noise in the results. - reported a couple of regressions/bisects * Misc (conf-calls, meetings, emails, ....) - support for M-profile related queries ( multilib etc...) == Next == * Validation - cleanup - reviews - armv8l vs arm - multiple gcc branches vs other components versions handling * GCC - trunk monitoring - some dev if time permits

9 years, 2 months

1
0
0 0

[ACTIVITY] Week 19

by Yvan Roux

== Progress == o Linaro GCC (5/10) * Linaro GCC 5.3 2016.05 snapshot - FSF branch merge + release * Linaro GCC 6.1 2016.05 snapshot - Create new branch + release o Extended validation (3/10) * Fixed validation issues when binary tarballs are created. o Misc (2/10) * Various meetings and discussions. == Plan == o Continue on validation/benchmarking o Catch up with upstream work.

9 years, 2 months

1
0
0 0

[ACTIVITY] 9-13 May 2016

by Diana Picus

== Progress == * Add a diag handler for llc so it doesn't exit on the first error it finds [TCWG-592] [5/10] - Started a discussion about a new diagnostic handler for llc - Patch accepted upstream, but broke a few things (Renato has investigated/fixed some of them - thanks) * Inline assembly constraints support for ARM [TCWG-560] [5/10] - Patch in upstream review, but should be committed after the new llc diagnostic is in place (otherwise it's difficult to test it meaningfully) == Plan == * Add a diag handler for llc so it doesn't exit on the first error it finds [TCWG-592] - Fix the remaining issues and get the patch committed again * Inline assembly constraints support for ARM [TCWG-560] - Rebase patch and try to get it reviewed * Investigate exit-on-error on LLC [TCWG-594] - Track the tests that need the exit-on-error flag with the new diagnostic handler

9 years, 2 months

1
0
0 0

[ACTIVITY] 9-13 May 2016

by Peter Smith

== Progress == - ldr rt,= implementation transform to MOV committed upstream [TCWG-468] [PR25722]] -- Thanks to Renato for committing. - Started looking at what would be needed to port lld to ARM -- The ELF lld port looks to have a fairly small amount of architecture specific hooks. Decided that I would learn fastest by just trying to do an ARM only prototype port to see if I could get hello world on linux working. -- spent too much time trying to think about how to best implement the group relocations for the PLT sequences then remembered that for a quick prototype I could use larger sequences that didn't need the relocations. == Plan == - Continue working on an ARM LLD port. Will hopefully have a good idea of what the scope of work needed is next week.

9 years, 2 months

1
0
0 0

[ANNOUNCE] Linaro GCC 5 and 6 2016.05 snapshots

by Yvan Roux

The Linaro Toolchain Working Group (TCWG) is pleased to announce the 2016.05 snapshot of both Linaro GCC 5 and Linaro GCC 6 source packages. Linaro GCC 6 monthly snapshot[1] is based on FSF GCC 6.1+svn236106 and includes performance improvements and bug fixes backported from mainline GCC. This snapshot contents will be part of the 2016.08 stable[2] quarterly release. This snapshot tarball is available on: http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.1-2016.05/ Interesting changes in this GCC source package snapshot include: * Updates to GCC 6.1+svn236106 Linaro GCC 5 monthly snapshot[1] is based on FSF GCC 5.3+svn236108 and includes performance improvements and bug fixes backported from mainline GCC. This snapshot contents will be part of the 2016.08 maintenance release. This snapshot tarball is available on: http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.05/ Interesting changes in this GCC source package snapshot include: * Updates to GCC 5.3+svn236108 * Backport of [Bugfix] [AArch32] PR target/70711 Fix big-endian ARMv8.1-A builds * Backport of [Bugfix] [AArch64] PR target/70044 -flto turns on -fomit-frame-pointer * Backport of [AArch32] Reduce size of arm1020e automaton * Backport of [AArch64] Fix SIMD predicate * Backport of [AArch64] Fix thinko in handling of -momit-leaf-frame-pointer option * Backport of [Testsuite] [AArch32] Tests for arm_restrict_it patterns in thumb2.md * Backport of [Testsuite] gcc-dg: handle all return values when shouldfail is set 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 * Interested in commercial support? inquire at "Linaro support": mailto:support@linaro.org [1]. Source package snapshots are defined when the compiler is only put through unit-testing and full validation is not performed. [2]. Stable source package releases are defined as releases where the full Linaro Toolchain validation plan is executed.

9 years, 2 months

1
0
0 0

[ACTIVITY] 2-6 May 2016

by Diana Picus

== Progress == * 3 days off (Mon/Thu/Fri) [6/10] * Inline assembly constraints support for ARM [TCWG-560] [3/10] - More investigations for PR24071; found the cause of the bug, working on a fix. * Rework LLVM helper scripts [TCWG-571] [1/10] - Addressed code review comments. - The interface changes to llvm-projs and llvm-sync are now committed. == Plan == * Inline assembly constraints support for ARM [TCWG-560] - Come up with a fix for PR24071 * Rework LLVM helper scripts [TCWG-571] - Investigate git worktree and how it could be factored into our scripts (llvm-projs, llvm-build)

9 years, 2 months

1
0
0 0

[ACTIVITY] Week 18

by Yvan Roux

o 2 days off (4/10) == Progress == o Extended validation (4/10) * Change extended native job to use multiple scm * Investigate validation issues when binary tarballs are created o Linaro GCC (1/10) * Finalized and submitted new Linaro development branch script. o Misc (1/10) * Various meetings and discussions. == Plan == o Create Linaro GCC 6 branches o Continue on validation and upstream work.

9 years, 2 months

1
0
0 0

[ACTIVITY] 2-6 May 2016

by Christophe Lyon

* 2 days off (Thu/Fri) == Progress == * Validation - restarted validations for pending backports, after the various branches updates - started looking at armv8l vs arm results differences * GCC - checked trunk regression reports - updated AArch32 Neon intrinsics tests. Patch series almost ready for submission * Misc (conf-calls, meetings, emails, ....) == Next == * Validation - cleanup - reviews - armv8l vs arm * GCC - trunk monitoring: check why builds were killed after timeout - more intrinsics tests

9 years, 2 months

1
0
0 0

[ACTIVITY] 2 - 6 May 2016

by Prathamesh Kulkarni

== This Week == * LTO (7/10) a) TCWG-548 (2/10) - Fixed a minor bug in the patch - Results of variable partitions with chromium: http://pastebin.com/fLD2JzgP - Significant difference in size of last partition could probably indicate sth wrong with patch (all unpartitioned variables go to last partition). b) TCWG-528 (3/10) - Posted upstream after bootstrap+test passed on ppc64le-linux-gnu - Addressed Richard's comments. c) TCWG-299 (2/10) - Firefox built on aarch64 natively (r1-a12) non LTO with gcc-5 branch - Fails to build with trunk due to issues in firefox codebase (PR70722) - Fails to build on armhf with following error: http://pastebin.com/9xydVtjj * TCWG-72 (2/10) - Rebased patch - Addressed Ramana's comments * Misc (1/10) - Meetings == This Week == - LTO: benchmark section anchors patch, submit patch for increase_alignment upstream, firefox - TCWG-72: Test and submit upstream

9 years, 2 months

1
0
0 0

[ACTIVITY] 02 - 06 May 2016

by Peter Smith

* Monday off [2/10] # Progress # * TCWG-468, ldr rt, =immediate Have a feature complete implementation. Passes existing regression tests. Still need to add more tests for new functionality and see if implementation can be tidied up a bit * Setting up a local chromebook to run the regression-tests. Should now be able to run test suite on ARM relatively easily. # Plan # * Complete TCWG-468 and send upstream for review. * Pick something else up.

9 years, 2 months

1
0
0 0

[ACTIVITY] 02 - 06 May 2016

by Yao Qi

* Monday off [2/10] # Progress # * TCWG-518, arm linux range stepping patches. [5/10] Tried different ways to manage breakpoints, but the program still gets SIGILL from time to time. Post my WIP patches upstream to see if people have some ideas on this. * TCWG-547, [1/10]. Try two approaches but give up due to the quite aggressive interface changes. Fortunately, the change in the third approach is quite small, testing the patch. * Misc, meeting, [2/10] # Plan # * TCWG-518, TCWG-547 -- Yao

9 years, 2 months

1
0
0 0

[ACTIVITY] 18 - 22 April 2016

by Kugan

== Progress == * GCC Stage-1 (5/10) - Posted patches and revised based on review - PR40921 and PR63586 - Getting ready post type promotion pass again * Linaro bug (2/10) - BUG 2195 and BIG 1979 - Investigation with trunk and educed test case shows Missing commit * Misc (1/10) - GCC Lists * Public holiday (2/10) == Plan == * Attend to pending stage1 patches

9 years, 2 months

1
0
0 0

[Weekly] 25-29 April 2016

by Michael Collison

== This week == * Bugzilla 69663 - [ARM] Implement overflow arithmetic standard names (0/10) - Pinged upstream; no response yet * Bugzilla 70089 - ARM/THUMB unnecessarily typecasts some rvalues on memory store (6/10) - Created updated patch that resolves 8/9 failures - Investigating execution failure on gcc.dg/fixed-point/convert-sat.c * TCWG-247 - Create Validation Job to run on GCC Trunk Commit (3/10) - Addressed all comments from code reviews and submitted final version * Misc (1/10) - Meetings == Next week == * Bugzilla 70089 - ARM/THUMB unnecessarily typecasts some rvalues on memory store - Resolve testsuite failure * Bugzilla 69663 - [ARM] Implement overflow arithmetic standard names (0/10) - Ping upstream

9 years, 2 months

1
0
0 0

[ACTIVITY] Week 17

by Yvan Roux

o 1 day off (2/10) == Progress == o Extended validation (2/10) * Extended validation now operational, reporting enhancements investigations. * Looked at gdb/guality unstable results. * Reviewed some jobs. o Linaro GCC (2/10) * Scripted new Linaro development branch process. o Upstream GCC (1/10) * Digging in libatomic code. o Misc (3/10) * Various meetings and discussions. == Plan == o 2 days off (Thu/Fri) o Continue on validation and upstream work.

9 years, 2 months

1
0
0 0

[ACTIVITY] 25-29 April 2016

by Prathamesh Kulkarni

== This Week == * LTO (6/10) a) TCWG-128 (1/10) - committed patch for adding param lto-max-partition, which can now be used as workaround for building chromium with minimal number of required partitions. - committed patch for setting default value of lto-min-partition to 10000. b) TCWG-528 (1/10) - Patch: http://people.linaro.org/~prathamesh.kulkarni/patch_increase_alignment.diff - Cross tested on arm*-*-*, aarch64*-*-* and bootstrapped and tested on aarch64-linux-gnu - I want to cross test once for ppc64 since that's also affected. c) TCWG-548 (4/10) - Patch: http://people.linaro.org/~prathamesh.kulkarni/patch-vars-3.diff - Cross tested for arm*-*-* and aarch64*-*-* * TCWG-319 (2/10) - Comparing diff's of vect for arm and armeb shows, armeb not supporting unaligned access - Looking thru arm backend code to see why this happens. * Validation (1/10) - Script to build chromium * Misc (1/10) - Looked at PR70848, PR60172 - Meetings == Next Week == LTO: section anchors, increase_alignment pass TCWG-319: Continue investigation Validation: Try to get the script merged to tcwg-buildapp repo.

9 years, 2 months

1
0
0 0

[ACTIVITY] 25 - 29 April 2016

by Peter Smith

# Progress # * TCWG-466, ADRL pseudo instruction support in integrated assembler. I couldn't find a way of putting ADRL into the assembler in a maintainable way. Managed to work out a pretty close approximation of ADRL in a macro so I added it to upstream PR. Put the results of the my investigations into TCWG-466. Agreed with Renato's initial diagnosis of won't fix. * TCWG-468, Transform LDR rn, =expr pseudo instruction into MOV. I'm more hopeful with this one. I've got a prototype that delays the emission of the constant pool entry to a point where the transformation can occur. * Try out the build and push scripts. Had a frustrating day of chasing down missing dependencies from my Ubuntu 12.04 machine while building lldb. Should be resolved now. # Plan # * UK national holiday on Monday. * Continue with TCWG-468. I've got a tablegen prototype that treats LDR rd,= as a real pseudo instruction. Need to finish Thumb and Thumb2. Next step after that is to do the transformation to MOV. * Will spend any other time investigating LLD

9 years, 2 months

1
0
0 0

[ACTIVITY] 25 - 29 April 2016

by Yao Qi

# Progress # * TCWG-518, range stepping on arm-linux. Rebase my patches, and choose a different approach which is better. However, GDBserver crashes in some cases, and I am investigating the crash. [5/10] * TCWG-547, make some progress on the upstream discussion. We agree to do it in a cleaner way but some GDB internal interface needs some changes. [2/10] * Read some articles about exception handling, this one is quite useful, https://gcc.gnu.org/ml/gcc/2002-07/msg00391.html [1/10] * Meeting, upstream patch review. [2/10] # Plan # * TCWG-518, TCWG-547 -- Yao

9 years, 2 months

1
0
0 0

[ACTIVITY] 25-29 April 2016

by Diana Picus

== Progress == * Rework LLVM helper scripts [TCWG-571] [4/10] - Code review + minor improvements to the scripts - Started a discussion about the interfaces of some of the scripts (llvm-projs, llvm-sync) * Inline assembly constraints support for ARM [TCWG-560] [3/10] - More investigations for PR24071 - Discovered that the assert is only triggered for aarch64-linux-gnueabi, whereas arm-linux-gnueabi behaves as expected (prints the error but doesn't assert afterwards). This has proven useful for figuring out the intended behavior of the code. * Move buildbots to CMake 3.4.3 [TCWG-573] [1/10] - Helped move some of the bots (llvm-a15-*) to CMake 3.4.3 * Misc [2/10] - Buildbot monitoring - Meetings == Plan == * Inline assembly constraints support for ARM [TCWG-560] - Come up with a fix for PR24071 * Rework LLVM helper scripts [TCWG-571] - Start a review for the new interface to llvm-projs/llvm-sync, so we can have some concrete support for further discussion - Investigate git worktree and how it could be factored into our scripts (llvm-projs, llvm-build) * Move buildbots to CMake 3.4.3 [TCWG-573] - Help with the llvm-chrome-* bots if necessary * OOO on Monday

9 years, 2 months

1
0
0 0

[ACTIVITY] 25-29 April 2016

by Christophe Lyon

== Progress == * Validation - armvl8 differences between master and stable branches understood (master defaulted to Thumb) - updated ABE stable branch for validation - ABE now uses linaro-local/stable DejaGnu branch - updated ABE legacy version to use this DJ branch too, and updated the Foundation Model path - updated Jenkins jobs accordingly * Backports - created a few backports for our gcc-5 branch, to prepare handover - slight documentation update * GCC - enhancements to validation harnesses to better handle infrastructure problems - using monitoring and regressions reports * Cortex-strings - updated a few aarch64 mem* routines from newlib versions * Support - finally reproduced the Windows-hosted toolchain bugs by rebuilding in a properly updated Jessie chroot. - building the next release in Trusty container should fix these problems * Misc (confi-calls, meetings, emails, ....) == Next == * Validation: cleanup & reviews * GCC - trunk monitoring, report regressions if needed - more intrinsics tests

9 years, 2 months

1
0
0 0

RE: [ACTIVITY] 18-22 April 2016

by Rob Savoye

As a note, all the builders we use for binary releases run Trusty still. I haven't tried Jessie (should work fine),but I know that newer Mingw releases fail to compile GCC 5.x. - rob - -------- Original message -------- From: Christophe Lyon <christophe.lyon(a)linaro.org> Date: 04/22/2016 14:00 (GMT-07:00) To: Linaro Toolchain Mailman List <linaro-toolchain(a)lists.linaro.org> Subject: [ACTIVITY] 18-22 April 2016 * 3 days off == Progress == * Validation: - fixed ABE master and stable branches to use 'ssh -t' instead of 'ssh -tt' when cross-testing - trying to assert master vs stable before the array branch merge, noticed differences on armv8l - created linaro-local/stable Dejagnu branch (currently a copy of master). Prepared ABE config patches to use it. * GCC - infrastructure problems (ST compute farm), leading to a lot of noise in the validations (and wrong regression reports upstream) - enabled gcc-6-branch monitoring - added GCC-6 tab to the backports spreadsheet * Support - Windows-hosted toolchain crashes: it seems the builders we use to make the release run Jessie and not Trusty. Tried to rebuild a toolchain in a Jessie chroot, but the script failed (works under Trusty) * Misc (conf-calls, meetings, emails, ...) == Next == * Validation - check that using linaro-local/stable Dejagnu branch works well - create validation reference points before array branch merge - understand/fix armv8l validation differences between master/stable ABE branches * GCC - trunk monitoring, report regressions if needed - more intrinsics tests * Support - Windows-hosted toolchain bug * Snapshots - prepare a few backports for our gcc-5 branch * Cortex-strings update _______________________________________________ linaro-toolchain mailing list linaro-toolchain(a)lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain

9 years, 2 months

3
6
0 0

[ACTIVITY] 18 - 22 April 2016

by Omair Javaid

== Progress == LLDB Chromebook Test Stability [TCWG-563] [3/10] -- Failures reduced to 15 fails and 4 errors after fixing stepping bug. -- Investigated remaining issues some of them are known issues and others will need further investigation. LLDB ARM Thread Stepping Problem [TCWG-566] [5/10] -- Problems caused because incorrect reporting of PLT entry size set by linker. -- Submitted a fix after analysis that logical size of PLT entry should be greater than 4bytes. -- Fix accepted and committed upstream. LLDB Buildbot Setup [TCWG-241] [1/10] -- Random change in results finally caught. It was due to inconsistent network. -- Progress halted to fix arm-linux-gnueabihf bugs. Miscellaneous [1/10] -- Meetings, emails, discussions etc. == Plan == LLDB Chromebook Test Stability [TCWG-563] -- Continue to resolve and investigate chromebook test failures. LLDB Buildbot Setup [TCWG-241] -- Start AArch64 tester evaluations.

9 years, 2 months

1
0
0 0

[ACTIVITY] Week 16

by Peter Smith

Progress: - On holiday all week, at ACCU conference. I've put some highlights at the end of the message. - Did some more investigation into TCWG-466 ADRL support in integrated assembler during breaks. -- Not looking good, to do this properly bumps up against a lot of design decisions and restrictions made by the LLVM assembler (designed as compiler target, not to be user friendly). -- There are ways it could be implemented with restrictions, but it is debateable whether it is worth doing at all. -- On the plus side I've got a much better idea of how the assembler works and what restrictions exist on each stage of the journey from a line in the .s file to emission in the object. Will add some comments to the LDR r0, =expr TCWG as well. -- On the negative side the :upper16: and :lower16: operators for MOVT and MOVW don't look to be correct in the presence of addends. Will need to investigate further to see what the scope of the problem is. Plan: - Dump results of TCWG-466 investigation into Jira. - Take a look at and post a comment on Adhemerval's revised TLS patch, even if it is just looks fine in the hope of pushing it forward a bit more. - Catch up with Renato's scripts and documents for LLVM sub-group. - Work out what to do with TCWG-466, if the answer is put it down, find something else to look at. ACCU Highlights/Report: Tough stuff in modern C++ A deep dive into some of the newer areas of C++ such as: - rvalue references and forwarding (universal) references - How to use SFINAE (mostly std::enable_if) to select algorithms optimised for particular template instantiations - Variadic templates. Including all sorts of strange ways to (ab)use expansion of parameter packs. C++ WG21 SG14 Gaming and low-latency study group - A new study group aiming to represent the gaming (primarily), but also embedded and high frequency trading concerns. - Motto seemed to be make sure "Don't pay for what you don't use" is enforced. Most interested in: -- No exceptions configurations -- No RTTI -- More performance out of the STL (see EA STL https://github.com/electronicarts/EASTL) -- Add ring buffers and support for unitialised memory, fixed point numbers, flat-map, standardised simd vector types Using sentinels - An example of how using two sentinels in an implementation of std::partion speeds up the algorithm by saving comparisons. Can speed up quicksort by a few percent Constexpr in C++14 - Example showing how you could build a string to enum map, operating entirely at compile time, and its subsequent negative effects on compile time! Concepts Lite - Concepts missed the C++17 standard, this presentation went into the current Technical Standard (optional) and how concepts would likely be implemented in C++(20?) - Not surprising to see that concepts still missed C++17 as there is only one implementation and one non-trivial use case (ranges) and there are still unresolved questions to be answered. Introduction to Julia - Really a comparison of Julia to the author's favoured language of common lisp. - Was impressed at how "lispy" Julia was whilst retaining high performance. - Liked the mathematical syntax - Didn't like the python like parts that seemed to be added to try and get people to migrate from python, but were non "lispy".

9 years, 2 months

1
0
0 0

[ACTIVITY] 18 - 22 April 2016

by Yao Qi

# Progress # * TCWG-545, patches are committed. Done. [3/10] * TCWG-167, ARM reverse debugging bug fixes. All test fails are fixed. Done. [2/10]. * PR 19947. The fix is approved, but the patch triggering the bug needs update. [2/10] * Help to fix broken ARM GDB after C++ switch. [2/10]. GDB mainline is a C++ program in default. Exception handling in GDB is broken on non-x86 host (ARM, AArch64, AIX, at least) because readline (C library) calls C++ GDB code, but exception unwinding can't cross the C function ("foreign frame"). The problem is fixed by catching all exceptions before return to readline, and re-throw them after return from readline back to GDB. * Misc, [1/10] ** Hack QEMU so that I can run gdb regression testsuite with qemu-arm. # Plan # * TCWG-518, rebase patches on mainline, test, and post patches if nothing wrong. * PR 19947, TCWG-561, * TCWG-547 -- Yao

9 years, 2 months

1
0
0 0

[ACTIVITY] Week 16

by Yvan Roux

== Progress == o Extended validation (5/10) * Created new extend validation job which handles native/cross validation and benchmarking. * Identified and discussed dejagnu Linaro branch issue. o Upstream GCC (2/10) * Start to look at libatomic ARMv8.1 support o Misc (3/10) * Various meetings * Support team members on benchmarking and validation. == Plan == o Continue on extended validation and Libatomic

9 years, 2 months

1
0
0 0

[ACTIVITY] 18 - 22 April 2016

by Prathamesh Kulkarni

== This Week == * LTO (5/10) a) Section anchors - another wasted prototype: http://pastebin.com/5MXFqrZY - will follow Richard's suggestion to put variable in partition that references it most, we can make this smarter incrementally if required. b) Retested patch for lto-max-partition c) Retested increase_alignment pass patch and wrote test cases for it. * Validation (2/10) a) Script to build chromium - works with armhf (with assumptions about my environment) - issues with gclient sync failure which in turn does not generate LASTCHANGE file causing build to fail. * Public Holiday (2/10) - Mahavir Jayanti * Misc (1/10) - Meetings == Next Week == - LTO: section anchors, post patches upstream for lto-max-partition and increase_alignment. - TCWG-319: Look at why armeb is failing to vectorize test-cases. - Validation: chromium

9 years, 2 months

1
0
0 0

[Weekly] 18-22 April 2016

by Michael Collison

== This week == * Bugzilla 67321 - [ARM] Exploit Wide Add operations when appropriate (1) - Re-based to GCC 6, re-validated and committed upstream * Bugzilla 70008 - [ARM] Reverse subtract with carry can be generated in thumb2 mode (1) - Re-based and re-validated - Need to create new bug as problem description does not match issue * Bugzilla 70089 - ARM/THUMB unnecessarily typecasts some rvalues on memory store (3/10) - Developed new patch for arm that detects failures with negative numbers - Debugging failures where constant is too large * TCWG-247 - Create Validation Job to run on GCC Trunk Commit (3/10) - Fleshed out additional portions of script and submitted for code review - Still issues to be resolved in script as noted in git review * Misc (2/10) - Meetings - Multiple interactions with ARM IT to configure and setup new laptop == Next week == * TCWG-247 - Finish script * Bugzilla 70089 - ARM/THUMB unnecessarily typecasts some rvalues on memory store - Finalize arm patch and validate * Bugzilla 70008 - create new bug and submit upstream patch

9 years, 2 months

1
0
0 0

[ACTIVITY] 18-22 April 2016

by Christophe Lyon

* 3 days off == Progress == * Validation: - fixed ABE master and stable branches to use 'ssh -t' instead of 'ssh -tt' when cross-testing - trying to assert master vs stable before the array branch merge, noticed differences on armv8l - created linaro-local/stable Dejagnu branch (currently a copy of master). Prepared ABE config patches to use it. * GCC - infrastructure problems (ST compute farm), leading to a lot of noise in the validations (and wrong regression reports upstream) - enabled gcc-6-branch monitoring - added GCC-6 tab to the backports spreadsheet * Support - Windows-hosted toolchain crashes: it seems the builders we use to make the release run Jessie and not Trusty. Tried to rebuild a toolchain in a Jessie chroot, but the script failed (works under Trusty) * Misc (conf-calls, meetings, emails, ...) == Next == * Validation - check that using linaro-local/stable Dejagnu branch works well - create validation reference points before array branch merge - understand/fix armv8l validation differences between master/stable ABE branches * GCC - trunk monitoring, report regressions if needed - more intrinsics tests * Support - Windows-hosted toolchain bug * Snapshots - prepare a few backports for our gcc-5 branch * Cortex-strings update

9 years, 2 months

1
0
0 0

[ACTIVITY] 18-22 April 2016

by Diana Picus

== Progress == * Inline assembly constraints support for ARM [TCWG-560] [1/10] - Started investigating Bug24071 * Intro to LLVM buildbots [1/10] - Got accustomed to the buildbot monitoring page - Learned how to connect to the bots/perform really basic maintenance * Misc [8/10] - Onboarding checklists, policies, meetings etc [6/10] - Laptop setup [2/10] == Plan == * Inline assembly constraints support for ARM [TCWG-560] - More investigations for Bug24071 * Misc - Finish reading Octopus policies - Review scripts for working with LLVM

9 years, 2 months

1
0
0 0

Cross compilation issue

by $rik＠nth

Hi All, I don't whether this is the right community mailing list to post support or not. Please correct me if i am wrong. I am trying to cross compile gcc to ARM as static binaries and as part of this, i am facing below issue. My build system is Ubuntu and using [1] gcc branch. Let me know what i can share more information to you. arm-linux-gnueabi-g++ -static -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -static-libstdc++ -static-libgcc -static -pthread -o xgcc gcc.o ggc-none.o \ c/gccspec.o libcommon-target.a \ libcommon.a ../libcpp/libcpp.a ../libbacktrace/.libs/libbacktrace.a ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a gcc.o:(.rodata+0x5acc): undefined reference to `host_detect_local_cpu(int, char const**)' collect2: error: ld returned 1 exit status make[2]: *** [xgcc] Error 1 [1] svn://gcc.gnu.org/svn/gcc/branches/linaro/gcc-4_8-branch -- Thanks & Regards, M.Srikanth Kumar.

9 years, 2 months

3
23
0 0

[ACTIVITY] 11 - 15 April 2016

by Omair Javaid

== Progress == LLDB Buildbot Setup [TCWG-241] [1/10] -- Created a new factory for LLDB buildbots. Halted plan to migrate till turning chromebook build green. LLDB Chromebook Test Stability [TCWG-563] [3/10] -- Investigated some failures some of them were fixed by a systemZ support large patch set. -- Failures reduced to 36 locally with some tweaks. Buildbot still showing random results. LLDB ARM Thread Stepping Problem [TCWG-566] [5/10] -- Only happening on Arm linux targets. -- Spent good bit of time debugging this issue. There are multiple problems but root cause is same. -- Initial investigation reveals frame unwinding issues from .plt section. Miscellaneous [1/10] -- Meetings, emails, discussions etc. == Plan == LLDB ARM Thread Stepping Problem [TCWG-566] -- Further debugging and investigation of this issue. -- Figure out a fix for stepping problem on arm linux.

9 years, 2 months

1
0
0 0

[ACTIVITY] Week 15

by Yvan Roux

== Progress == o GCC 2016.04 source snapshot (4/10) * Reviewed on-going backports * Merged from FSF GCC 5 branch * Packaged and released snaphot o Extended validation (3/10) * Native validation identifies upstream issues - Fixed Glibc warnings raised by GCC 6, committed in Glibc master * Looking at bkk16 job switch to multijob.. o Misc (3/10) * Various meetings == Plan == o Continue on extended validation o GCC ARMv8.1 builtins fix.

9 years, 2 months

1
0
0 0

[Weekly] 11-15 April 2016

by Michael Collison

== This week == * Bugzilla 70089 - ARM/THUMB unnecessarily typecasts some rvalues on memory store (1/10) - Arm backend is not recognizing that some constants can be encoded using modified immediate - This is causing constant to be split and additional code generated - Range of constants allowed differs between Arm and Thumb2 - Created prototype patch to allow additional ARM modified immediate instructions - Began work on Thumb2 patch * TCWG-247 - Create Validation Job to run on GCC Trunk Commit (2/10) - Developed shell portion of script to read and parse web page with builder information - Developing rest of yaml script including trigger on specified interval * Misc meeting (1/10) * Vacation (6/10) - April 11 - 13 == Next week == * TCWG-247 - Finish script * Bugzilla 70089 - ARM/THUMB unnecessarily typecasts some rvalues on memory store - Finalize arm patch and validate - Make progress on Thumb2 patch

9 years, 2 months

1
0
0 0

[ACTIVITY] 11-15 April 2016

by Prathamesh Kulkarni

== This Week == * LTO (5/10) a) Section anchors: - 3 iterations of prototype patch - Validated with testsuite and chromium LTO build - Submitted prototype patch upstream: https://gcc.gnu.org/ml/gcc/2016-04/msg00090.html * Bugs (1/10) - Looked at bugs 2073 and 2174 * Public Holidays (4/10) - Dr Ambedkar Jayanti and Ram Navami == Next Week == - LTO: section anchors, benchmarking - Validation: chromium

9 years, 2 months

1
0
0 0

[ACTIVITY]

by Renato Golin

== Progress == * Support (2/10) - Closing some inline asm constraint bugs that were fixed or user error - Finished PR16275 * Background (8/10) - Code review, meetings, discussions, general support, etc. - Lost track of how many meetings and email threads I had - Mostly about helping newcomers, managing Android/LLDB/LLD expectations - Also hardware planning, LLVMLinux revival, checking Swift

9 years, 3 months

1
0
0 0

[ACTIVITY] 11 - 15 April 2016

by Peter Smith

Progress: - Read up on AARCH64 TLS and LLD code base - Commented on upstream patch in hope of getting approval from the code-owners - TCWG-466 Implement ADRL pseudo in LLVM assembler -- Slow progress as the pseudo instruction does not fit well into the existing architecture -- On the positive side I have learned quite a bit about how the LLVM assembler works -- Will make a decision next week whether it is worth actively pursuing TCWG-466. Supporting ADRL is not high priority and whatever fix I come up with may be difficult to get accepted upstream. I'd still like to keep trying, at least as a background task, but I think that there is higher priority work that can be done instead. Next Week: On holiday (hopefully added correctly to Linaro google calendar). I'll be at the ACCU conference.

9 years, 3 months

1
0
0 0

[ACTIVITY] 11-15 April 2016

by Christophe Lyon

== Progress == * Validation - finally identified what caused several random results: use of 'ssh -tt' to acces the remote tester. I don't know the real cause. * GCC - reported a few regressions in trunk - a few backports - AdvSIMD intrinsics tests: built the list of AArch64 intrinsics not yet covered - support on a few bug reports * Misc (conf-calls, meetings, emails, ....) == Next == * Holidays Mon/Tue/Wed * Validation - consolidation on stdout/stderr problems - extended validation * GCC: - trunk monitoring, report regressions if needed - start monitoring the just-created gcc-6 branch - more intrinsics tests - switch backport activity to gcc-6 branch, update tools, etc...

9 years, 3 months

1
0
0 0

[ACTIVITY] 11 - 15 April 2016

by Yao Qi

# Progress # * TCWG-545, 7 patches are approved, and 1 patch needs update, which needs the change somewhere else. [3/10] * TCWG-547, patch is pending. Pinged Pedro on IRC, to be reviewed, but no response. * TCWG-167, [3/10]. ARM reverse debugging fixes. Post one patch to fix test case. Testing another patch to give high priority of epilogue unwinder. * Upstream patch review, [2/10]. Spend more time on this due to long patch review backlog. The more I reviewed, the sooner my patches will be reviewed by others. * Misc, [2/10] ** Look at the slowness of gdb regression test in jekins validation, but can't reproduce it. ** Share some knowledge of watchpoint implementation in GDB to the people, who need the equivalent or similar things in LLDB. # Plan # * TCWG-545, TCWG-547, TCWG-167. -- Yao

9 years, 3 months

1
0
0 0

[ANNOUNCE] Linaro GCC 5 2016.04 snapshot

by Yvan Roux

The Linaro Toolchain Working Group (TCWG) is pleased to announce the 2016.04 snapshot of the Linaro GCC 5 source package. This monthly snapshot[1] is based on FSF GCC 5.3+svn234898 and includes performance improvements and bug fixes backported from mainline GCC. This snapshot contents will be part of the 2016.05 stable [1] quarterly release. This snapshot tarball is available on: http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.04/ Interesting changes in this GCC source package snapshot include: * Updates to GCC 5.3+svn234898 * Backport of [Bugfix] [AArch32] Fix PR target/70496 * Backport of [Bugfix] [AArch32] PR driver/70132: Avoid double fclose in driver-arm.c * Backport of [Bugfix] [AArch32] PR rtl-optimization/69904: Disallow copying/duplicating of load-exclusive operations * Backport of [Bugfix] [AArch32] PR target/62254 Fix for ARMv3 * Backport of [Bugfix] [AArch32] PR target/69614 * Backport of [Bugfix] [AArch32] PR target/70566 Check that condition register is dead in tst-imm -> lsls-imm Thumb2 peepholes * Backport of [Bugfix] [AArch32] PR testsuite/70553 * Backport of [Bugfix] [AArch64] PR rtl-optimization/70398 LRA * Backport of [Bugfix] PR 69400: Invalid 128-bit modulus result * Backport of [Bugfix] PR middle-end/70370 * Backport of [AArch32] 1/2 Cortex-R8 support * Backport of [AArch32] Add initial support for the Cortex-A32 * Backport of [AArch32] Add support for Cortex-A35 * Backport of [AArch32] Delete ASM_OUTPUT_DEF and fall back to default .set directive * Backport of [AArch64] 1/3 Enable CRC by default for armv8.1-a * Backport of [AArch64] 2/3 Rework the code to print extension strings (pr70133) * Backport of [AArch64] 3/3 Fix up for pr70133 * Backport of [AArch64] [ACLE][NEON] Implement vcvt*_s64_f64 and vcvt*_u64_f64 NEON intrinsics * Backport of [AArch64] Add extra tuning parameters for target processors * Backport of [AArch64] Add support for Cortex-A35 * Backport of [AArch64] Only update assembler .arch directive when necessary * Backport of [Testsuite] [AArch32] 2/2 Cortex-R8 support * Backport of [Testsuite] [AArch64] PR target/70113 fix pr63304_1 testcase * Backport of [Testsuite] [AArch64] Skip gcc.target/aarch64/assembler_arch_1.c if assembler does not support it * Backport of [Testsuite] Avoid GDB being blocked on signals * Backport of [Testsuite] Fix testsuite for Cortex-R8 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 * Interested in commercial support? inquire at "Linaro support": mailto:support@linaro.org [1]. Stable source package releases are defined as releases where the full Linaro Toolchain validation plan is executed. [2]. Source package snapshots are defined when the compiler is only put through unit-testing and full validation is not performed.

9 years, 3 months

1
0
0 0

[ACTIVITY] 4 - 8 April 2016

by kugan

== Progress == * Type promotion pass (2/10) - Benchmarking * LTO (7/10) - Refactoring tree-vrp to share common parts - Looking at open enhancement bugzilla and working on them * Misc (1/10) - GCC Lists == Plan == * LTO and VRP

9 years, 3 months

1
0
0 0

[ACTIVITY] 4 - 8 April 2016

by Omair Javaid

== Progress == LLDB Buildbot Setup [TCWG-241] [9/10] -- Migration of local master/slave setup to Linaro LLVM lab. -- Setup slave to be able to connect to chromebook for lldb remote testing. -- Modified Android build scripts to work with chromebook in llvm lab. Miscellaneous [1/10] -- Meetings, emails, discussions etc. == Plan == LLDB Buildbot Setup [TCWG-241] -- Write a new factory for linux based lldb script commands -- Break down and tweak scripts with better logical steps. -- Migrate current setup to use new factory. LLDB development [TCWG-563] -- Look into failing tests on chromebook tester and see if some of them can be fixed.

9 years, 3 months

1
0
0 0

[ACTIVITY] Week 14

by Yvan Roux

== Progress == o Extended validation (5/10) * Dejagnu remote layout patch finalized and committed upstream (will be part of the coming 1.6 Dejagnu release) * GCC guality test fix committed in trunk. * Native armv8l validation unblocked, but still slow (more than 8hrs) Analysis on-going. * Start to work on enhancement: include cross validation and benchmark trigger. o Misc (5/10) * Lot of meetings (Internal, training, Benchmarking, ...) == Plan == o Monthly snaphsot (review backports, branch merge) o Continue on extended validation o GCC ARMv8.1 builtins fix.

9 years, 3 months

1
0
0 0

[ACTIVITY] 4 - 8 April 2016

by Prathamesh Kulkarni

== This Week == * LTO (6/10) a) tcwg-128: branch out of range error - Addressing upstream reviews - Patch needs approval from Honza b) section-anchors - Understanding balanced partitioning algorithm - Working on 2nd prototype: http://people.linaro.org/~prathamesh.kulkarni/section-anchors-1.diff - Looking at regressions caused due to patch: http://people.linaro.org/~prathamesh.kulkarni/section-anchors-1-compare-res… c) submitted patch to slightly refactor lto_balanced_map: - https://gcc.gnu.org/ml/gcc-patches/2016-04/msg00341.html d) tcwg-534: ipa-comdats - found why ICE happens e) ipa-vrp - Discussions with Kugan * Validation (1/10) - Passing -static-libstdc++ works to build chromium without using chromium's sysroot. - Review 11311 - Untested script to build chromium for arm, x86: http://people.linaro.org/~prathamesh.kulkarni/build-chromium.sh * Public Holiday (2/10) * Misc (1/10) - Meetings == Next Week == - LTO: section anchors - Validation

9 years, 3 months

1
0
0 0

[ACTIVITY] for week ending 8th April 2016

by Peter Smith

== Progress == Transition week into Linaro toolchain group from ARM to replace Bernie [*] - Some ARM handover work done. - Started looking into https://llvm.org/bugs/show_bug.cgi?id=24350 (TCWG-466 ADRL support) -- Checked behaviour of ADRL on armasm and GNU as -- Worked out what I need to do in LLVM to make ADRL work, looks like nothing hugely complicated but a lot of plumbing through various layers. - Started reading about AArch64 TLS descriptor implementation. I'm familiar with the AArch32 traditional model so I need to bridge the gap a bit. == Plans == - Post some review comments on Adhemeval's TLS patch with the hope of unblocking it. - Start implementing support for ADRL in the integrated assembler == Planned Absences == Holiday 18th - 22nd April (Attending ACCU conference in Bristol). I think I've put that in the shared holiday calendar correctly. [*] Hello to everyone I didn't manage to meet at Linaro Connect. I've been working in ARM's proprietary compiler team, with much of that time spent on armlink and the other non-compiler tools.

9 years, 3 months

1
0
0 0

[ACTIVITY]

by Renato Golin

== Progress == * Support (2/10) - Adding more tests to D18701, covering more cases - Investigating PR27250 (user error) * Buildbots (2/10) - More work around LLDB buildbots * Background (6/10) - Code review, meetings, discussions, general support, etc. - Android / AOSP discussions, meetings - Some lab planning, meetings - Helping newcomers, meetings

9 years, 3 months

1
0
0 0

[ACTIVITY] 1 April -- 8 April

by Yao Qi

# Progress # * TCWG-167, ARM reverse debugging bug fixes. [4/10] Four patches are committed. All FAILs are fixed if test case is compiled with -fomit-frame-pointer. Some FAILs when -fno-omit-frame-pointer are caused by epilogue unwinder doesn't parse epilogue correctly if FP is involved. File TCWG-562 to track it. * TCWG-545, TCWG-547, patches are pending. Maintainer is busy on something else. * Triage the regression gdb.base/jit.exp. [1/10] We need a pending patch series to address this issue. Ask Pedro how to review them. * TCWG-561, handle unavailable memory during frame unwinding. [3/10] Think about it and write a prototype. * Misc, patches review and meeting, [2/10]. # Plan # * Take a look at the slow native arm-linux-gnueabihf gdb test. * TCWG-562, Tweak epilogue unwinder to handle FP. * TCWG-545, TCWG-547, ping. * TCWG-561, finish the prototype. -- Yao

9 years, 3 months

1
0
0 0

Linaro toolchain: libstdc++.so: file format not recognized; treating as linker script

by Gunnar Arndt

My dear friends, I'm trying to build C++ code for Linux running on am ARM Cortex A8 (TI AM335x). For a first try, I'm using the simplest program I can think of: /* main.cpp */ int main() { return 0; } Under Linux with the 'normal' GCC, that works fine, but under Windows 7 with the Linaro toolchain, it fails with the following message: C:\firedect\dev\workspace\Test-Linux-ARM_1> "\Program Files (x86)\GNU Tools ARM Embedded\gcc-linaro-4.9-2016.02-i686-ming w32_arm-linux-gnueabi\bin\arm-linux-gnueabi-g++.exe" main.cpp c:/program files (x86)/gnu tools arm embedded/gcc-linaro-4.9-2016.02-i686-mingw32_arm-linux-gnueabi/bin/../lib/gcc/arm-linux-gnueabi/4.9.4/../../../../arm-linux-gnueabi/bin/ld.exe:c:/program files (x86)/gnu tools arm embedded/gcc-linaro-4.9-2016.02-i686-mingw32_arm-linux-gnueabi/bin/../lib/gcc/arm-linux-gnueabi/4.9.4/../../../../arm-linux-gnueabi/lib/libstdc++.so: file format not recognized; treating as linker script c:/program files (x86)/gnu tools arm embedded/gcc-linaro-4.9-2016.02-i686-mingw32_arm-linux-gnueabi/bin/../lib/gcc/arm-linux-gnueabi/4.9.4/../../../../arm-linux-gnueabi/bin/ld.exe:c:/program files (x86)/gnu tools arm embedded/gcc-linaro-4.9-2016.02-i686-mingw32_arm-linux-gnueabi/bin/../lib/gcc/arm-linux-gnueabi/4.9.4/../../../../arm-linux-gnueabi/lib/libstdc++.so:1: syntax error collect2.exe: error: ld returned 1 exit status C:\firedect\dev\workspace\Test-Linux-ARM_1> "\Program Files (x86)\GNU Tools ARM Embedded\gcc-linaro-5.3-2016.02-i686-ming w32_arm-linux-gnueabihf\bin\arm-linux-gnueabihf-g++.exe" main.cpp c:/program files (x86)/gnu tools arm embedded/gcc-linaro-5.3-2016.02-i686-mingw32_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-gnueabihf/5.3.1/../../../../arm-linux-gnueabihf/bin/ld.exe:c:/program files (x86)/gnu tools arm embedded/gcc-linaro-5.3-2016.02-i686-mingw32_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-gnueabihf/5.3.1/../../../../arm-linux-gnueabihf/lib/libstdc++.so: file format not recognized; treating as linker script c:/program files (x86)/gnu tools arm embedded/gcc-linaro-5.3-2016.02-i686-mingw32_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-gnueabihf/5.3.1/../../../../arm-linux-gnueabihf/bin/ld.exe:c:/program files (x86)/gnu tools arm embedded/gcc-linaro-5.3-2016.02-i686-mingw32_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-gnueabihf/5.3.1/../../../../arm-linux-gnueabihf/lib/libstdc++.so:1: syntax error collect2.exe: error: ld returned 1 exit status As you can see, I have tested two versions of the toolchain, which show the same behavior. Do you have any idea what's going wrong here? I'd appreciate any help you can provide! -- Kind regards, Gunnar Arndt

9 years, 3 months

3
8
0 0

Another weird behavior with arm gcc 5.3

by fengwei.yin

Hi list, I hit another weird problem after use gcc 5.3 (If I use gcc 4.9, there is no any issue) with android. With arm gcc 5.3, the C++ apps crash in one class constructor call. And gdb shows some vtbl items of the class are not relocated. With arm gcc 4.9, if set breakpoint in that constructor, we could see the vtbl items of the class are relocated. And Yes. I know the android bionic loader take response to do relocation. But if it works with gcc 4.9, I suppose bionic loader work well (unless gcc 5.3 create some new situation not handled by it). I attached the vtbl dump in gdb for gcc 5.3 and 4.9 both. We could see all valid entries in vtbl are relocated in 4.9 dump. But not all entries in vtbl are relocated in 5.3 dump (the address is not started with 0xf). Suggestions/hints are welcome. Thanks a lot. Regards Yin, Fengwei

9 years, 3 months

3
7
0 0

[ACTIVITY] 27 March to 1 April 2016

by kugan

== Progress == * Type promotion pass (4/10) - Tested many different architectures - Branch created - Getting ready to benchmark * LTO (2/10) - Read VRP algorithms - new - Discussing algorithm implementation * Bugs (1/10) - PR70359 * Misc (1/10) - GCC Lists - Jenkins benchmarking jobs * Public holiday (2/10) == Plan == * LTO and VRP

9 years, 3 months

1
0
0 0

Re: Question regarding the arm gcc 5.3 to build android

by Jim Wilson

On Thu, Mar 31, 2016 at 5:12 AM, fengwei.yin <fengwei.yin(a)linaro.org> wrote: > Because gcc 4.9 could build this file without any issue, I apply > --save-temps > with gcc 4.9. The ii file is attached. Can't see significant differences. There is a patch in gcc-5 to make unified assembler syntax the default. Unfortunately, it changes how extended asms work, which is perhaps a bug. The message claims it doesn't affect extended asms, but it does. https://gcc.gnu.org/ml/gcc-patches/2015-11/msg01196.html The interesting bit is the change to ASM_APP_OFF. gcc-4.9 emits a .thumb after the extended asm to switch back into thumb mode just in case. gcc-5.3 instead emits .syntax unified, which doesn't change the arm/thumb mode, just the syntax supported. This is arguably a bug, but this doesn't immediately help you. It could take a little time to get gcc-5.x source fixed, and then the compiler binary releases. Or alternatively we could fix the asm to work with gcc 5. Jim

9 years, 3 months

4
7
0 0

[ACTIVITY] Week 13

by Yvan Roux

== Progress == o Extended validation (7/10) * Fixed and improved extended native validation * Discussed proposed patch in dejagnu on process killing mechanism * Testing a fix/workaround in GCC guality tests * Re-implemented and tested fix for dejagnu remote layout o Misc (3/10) * Various meetings == Plan == o Continue on extended validation o Finalize DejaGNU patches, GCC ARMv8.1 builtins fix.

9 years, 3 months

1
0
0 0

[Weekly] 28 March - 01 Apr

by Michael Collison

== This week == * Bugzilla 69008 - gcc emits unneeded memory access when passing trivial structs by value (ARM) (3/10) - Additional investigation and preliminary implementation * Bugzilla 70089 - ARM/THUMB unnecessarily typecasts some rvalues on memory store (1/10) - Investigation * TCWG-247 - Create Validation Job to run on GCC Trunk Committ (5/10) - Began writing shell script. * Misc meeting (1/10) == Next week == * TCWG-247 - Make additional prgoress on prototype * Bugzilla 69008 - gcc emits unneeded memory access when passing trivial structs by value (ARM) - Additional investigation and preliminary implementation * Bugzilla 70089 - ARM/THUMB unnecessarily typecasts some rvalues on memory store - Investigation * Vacation - April 8 - April 12

9 years, 3 months

1
0
0 0

[ACTIVITY]

by Renato Golin

== Progress == * Holiday (2/10) * Support (1/10) - Reapplying fix for PR16275 (D18701) - Conclusion is that original approach will be the same as GCC - Additional flags will have to be agreed upon across compilers * Buildbot (2/10) - Setting up LLDB buildbot with Omair - Precarious infrastructure is unstable, hope it holds on until the new rack is complete * Background (5/10) - Code review, meetings, discussions, general support, etc. - More team management stuff (access/procedure/meeting with newcomers) - Planning the lab move, resources, costs, schedule

9 years, 3 months

1
0
0 0

[ACTIVITY] 28 March -- 01 April

by Yao Qi

* Monday off [2/10] # Progress # * TCWG-167, ARM reverse debugging bug fixes. [4/10] Two patches are posted. Two patches are being tested. They fix 207 FAILs (242 -> 35) in gdb.reverse. * TCWG-545, no progress, patches are pending for review. * TCWG-547, [2/10]. Write a patch as Pedro suggested, so we have sense which patch is better. No response. * Misc, [2/10] ** Upstream discussions on get syscall number on execve exit. Can't get such thing from kernel side, need to figure out how to do it in GDB side. ** Investigate a little bit on 32-bit DWARF on AArch64. # Plan # * TCWG-167, TCWG-545, TCWG-547 -- Yao

9 years, 3 months

1
0
0 0

[ACTIVITY] 28 March-1 April 2016

by Christophe Lyon

* Monday off (2/10) == Progress == * Validation - extended validation - dejagnu and stdout/stderr possible races * GCC - reported a few regressions in trunk and gcc-5 branch - a few backports * Misc (confi-calls, meetings, emails, ....) == Next == * Validation - extended validation - more on dejagnu stdout/stderr & random results * GCC: - trunk monitoring, report regressions if needed - intrinsics tests cleanup - backports

9 years, 3 months

1
0
0 0

[ACTIVITY] 27 March to 1 April 2016

by Prathamesh Kulkarni

== This Week == * LTO (7/10) a) TCWG-534 (ipa-comdats): - Patch posted upstream: https://gcc.gnu.org/ml/gcc/2016-03/msg00254.html - Investigating ICE with patch for comdat-2.C b) TCWG-128 (branch out of range error): - Posted patch upstream: https://gcc.gnu.org/ml/gcc-patches/2016-04/msg00032.html c) intra-procedural vrp: - Looking to implement replacement_order algorithm for early vrp from the paper: https://engineering.purdue.edu/paramnt/publications/1381.pdf * Validation (2/10) - Reviews on tcwg-buildapp from Christophe and Maxim - prototype job ran successfully. * Misc (1/10) - Meetings == Next Week == * LTO: - Try to implement replacement order algorithm for vrp - Continue investigating ipa-comdats ICE and address upstream comments. - Gather stats for chromium LTO build * Validation: - write script to build chromium

9 years, 3 months

1
0
0 0

Support for ARM v8.2

by Vitali Sokhin

Hi all, Is there a roadmap for adding support for ARMv8.2 ? Specifically for assembler to support new instructions and SPRs? Thank you, Vitali

9 years, 3 months

3
2
0 0

Re: Question regarding the arm gcc 5.3 to build android

by Jim Wilson

On Wed, Mar 30, 2016 at 6:26 PM, fengwei.yin <fengwei.yin(a)linaro.org> wrote: > Thanks a lot for your quick response. The .ii file was attached. In UnwindFromContext, there is an asm that forces the assembler into ARM mode. if (ucontext == nullptr) { int ret = (({ unw_tdep_context_t *unw_ctx = (&context_); register unsigned \ long *unw_base asm ("r0") = unw_ctx->regs; __asm__ __volatile__ ( ".align 2\nbx\ pc\nnop\n.code 32\n" "stmia %[base], {r0-r15}\n" "orr %[base], pc, #1\nbx %[ba\ se]" : [base] "+r" (unw_base) : : "memory", "cc"); }), 0); The ".code 32" puts us in ARM mode. GCC still thinks that we are in thumb mode though, and continues to emit thumb instructions, some of which have no arm mode equivalent, e.g. cbnz and cbz. I don't see any convenient push/pop for thumb/arm mode. This is probably a macro expanded into the asm. You could have two versions of the asm, one that gets used when __thumb__ is defined and one that gets used when __thumb__ is not defined. The __thumb__ version would switch back into thumb mode at the end with a ".thumb" pseudo-op. Or alternatively, don't build with -mthumb. Jim

9 years, 3 months

2
1
0 0

Question regarding the arm gcc 5.3 to build android

by yfw

Hi folks, I am trying to use arm gcc 5.3 to build part of android AOSP and hit following issue with arm gcc 5.3: The gcc cmd line is like: /opt/work/acadine/mem_shrink/B2G-v2.5/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-5.3-linaro/bin/arm-linux-androideabi-g++ -I external/libcxx/include -I system/core/libbacktrace -I out/target/product/linaro_arm/obj/SHARED_LIBRARIES/libbacktrace_intermediates -I out/target/product/linaro_arm/gen/SHARED_LIBRARIES/libbacktrace_intermediates -I libnativehelper/include/nativehelper -I system/core/base/include -I external/libunwind/include -isystem system/core/include -isystem system/media/audio/include -isystem hardware/libhardware/include -isystem hardware/libhardware_legacy/include -isystem hardware/ril/include -isystem libnativehelper/include -isystem frameworks/native/include -isystem frameworks/native/opengl/include -isystem frameworks/av/include -isystem frameworks/base/include -isystem out/target/product/linaro_arm/obj/include -isystem bionic/libc/arch-arm/include -isystem bionic/libc/include -isystem bionic/libc/kernel/uapi -isystem bionic/libc/kernel/uapi/asm-arm -isystem bionic/libm/include -isystem bionic/libm/include/arm -c -fno-exceptions -Wno-multichar -msoft-float -ffunction-sections -fdata-sections -funwind-tables -fstack-protector -Wa,--noexecstack -Werror=format-security -D_FORTIFY_SOURCE=2 -fno-short-enums -no-canonical-prefixes -fno-canonical-system-headers -march=armv7-a -mfloat-abi=softfp -mfpu=vfpv3-d16 -include build/core/combo/include/arch/linux-arm/AndroidConfig.h -I build/core/combo/include/arch/linux-arm/ -Wno-psabi -mthumb-interwork -DANDROID -fmessage-length=0 -W -Wall -Wno-unused -Winit-self -Wpointer-arith -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -DNDEBUG -g -Wstrict-aliasing=2 -fgcse-after-reload -frerun-cse-after-loop -frename-registers -DNDEBUG -UDEBUG -fvisibility-inlines-hidden -DANDROID -fmessage-length=0 -W -Wall -Wno-unused -Winit-self -Wpointer-arith -Wsign-promo -std=gnu++11 -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -DNDEBUG -UDEBUG -mthumb -Os -fomit-frame-pointer -fno-strict-aliasing -fno-rtti -Wall -Werror -fPIC -D_USING_LIBCXX -std=gnu++11 -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -MD -MF out/target/product/linaro_arm/obj/SHARED_LIBRARIES/libbacktrace_intermediates/UnwindCurrent.d -o out/target/product/linaro_arm/obj/SHARED_LIBRARIES/libbacktrace_intermediates/UnwindCurrent.o system/core/libbacktrace/UnwindCurrent.cpp And I got error: /tmp/ccZ40ViQ.s: Assembler messages: /tmp/ccZ40ViQ.s:1752: Error: selected processor does not support ARM mode `cbnz r6,.L91' /tmp/ccZ40ViQ.s:1758: Error: selected processor does not support ARM mode `cbnz r0,.L92' /tmp/ccZ40ViQ.s:1763: Error: selected processor does not support ARM mode `cbz r1,.L107' /tmp/ccZ40ViQ.s:1941: Error: selected processor does not support ARM mode `cbz r6,.L100' But if I use the arm gcc 4.9, there is no any build issue. the "-dumpspecs" output of gcc 5.3 was attached. Thanks. Regards Yin, Fengwei

9 years, 3 months

2
1
0 0

[ANNOUNCE] Linaro Binary Toolchain Release GCC 4.9-2016.02

by Ryan Arnold

The Linaro Binary Toolchain ============================ The Linaro GCC 4.9-2016.02 Release is now available. Notice: All Linaro GCC 4.9 series toolchain users should migrate to the latest version of the Linaro GCC 4.9 toolchain in order to mitigate potential security exposure to CVE-2015-7545. See the NEWS section below for details. Download release packages from: http://releases.linaro.org/components/toolchain/gcc-linaro/4.9-2016.02/ http://releases.linaro.org/components/toolchain/binaries/4.9-2016.02/ Previous snapshots and release-candidates are at: http://snapshots.linaro.org/components/toolchain/binaries/ Previous releases are at: http://releases.linaro.org/components/toolchain/binaries/ Host Requirements ================== Linaro officially supports the current and previous Ubuntu LTS releases (as of the time of this release). This does not mean that the toolchain will not work on other/older Linux distributions. See the following for the life-time of Ubuntu LTS releases. https://wiki.ubuntu.com/Releases The host system upon which the cross-compiler will run requires a minimum of glibc 2.14, because of API changes to glibc's memcpy API. https://bugs.linaro.org/show_bug.cgi?id=1869 Package Versions ================= Linaro GCC 4.9-2016.02 FSF eglibc 2.19 (eglibc.git/linaro_eglibc-2_19) Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch) Linaro binutils 2.24 (linaro_binutils-2_24-branch) FSF GDB 7.10 (gdb-7.10-branch) Linaro Linux Version 3.17-2014.10 (linux-linaro-3.17-2014.10) Linaro toolchain package git branches are hosted at: http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search NEWS for Linaro GCC 4.9-2016.02 ================================ * The armv8l-linux-gnueabihf targetted toolchain is now built using --with-mode=thumb (like all of the other cross toolchains) rather than the default which is ARM mode. * Applied fix for CVE-2015-7545 - A stack-based buffer overflow in glibc's getaddrinfo() was corrected in glibc 2.23 and backported into Linaro eglibc 2.19 (linaro_eglibc-2_19). https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html * See the following Linaro GCC snapshot: http://snapshots.linaro.org/components/toolchain/gcc-linaro/4.9-2015.10/ Contact Linaro =============== File bugs at http://bugs.linaro.org For Linaro member support see http://support.linaro.org For Linaro community support email linaro-toolchain(a)lists.linaro.org -- Ryan S. Arnold | Linaro Toolchain Engineering Manager ryan.arnold(a)linaro.org | ryanarn on #linaro-tcwg @ freenode.irc.net

9 years, 3 months

1
0
0 0

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 4.9-2016.02-rc1

by Ryan Arnold

The Linaro Binary Toolchain ============================ The Linaro GCC 4.9-2016.02-rc1 Release-Candidate is now available. Notice: All Linaro GCC 4.9 series toolchain users should migrate to the latest version of the Linaro GCC 4.9 toolchain in order to mitigate potential security exposure to CVE-2015-7545. See the NEWS section below for details. Download release-candidate packages from: http://snapshots.linaro.org/components/toolchain/gcc-linaro/4.9-2016.02-rc1/ http://snapshots.linaro.org/components/toolchain/binaries/4.9-2016.02-rc1/ Previous snapshots and release-candidates are at: http://snapshots.linaro.org/components/toolchain/binaries/ Previous releases are at: http://releases.linaro.org/components/toolchain/binaries/ Host Requirements ================== Linaro officially supports the current and previous Ubuntu LTS releases (as of the time of this release). This does not mean that the toolchain will not work on other/older Linux distributions. See the following for the life-time of Ubuntu LTS releases. https://wiki.ubuntu.com/Releases The host system upon which the cross-compiler will run requires a minimum of glibc 2.14, because of API changes to glibc's memcpy API. https://bugs.linaro.org/show_bug.cgi?id=1869 Package Versions ================= Linaro GCC 4.9-2016.02-rc1 FSF eglibc 2.19 (eglibc.git/linaro_eglibc-2_19) Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch) Linaro binutils 2.24 (linaro_binutils-2_24-branch) FSF GDB 7.10 (gdb-7.10-branch) Linaro Linux Version 3.17-2014.10 (linux-linaro-3.17-2014.10) Linaro toolchain package git branches are hosted at: http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search NEWS for Linaro GCC 4.9-2016.02-rc1 ==================================== * Applied fix for CVE-2015-7545 - A stack-based buffer overflow in glibc's getaddrinfo() was corrected in glibc 2.23 and backported into Linaro eglibc 2.19 (linaro_eglibc-2_19). https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html * See the following Linaro GCC snapshot: http://snapshots.linaro.org/components/toolchain/gcc-linaro/4.9-2015.10/ Contact Linaro =============== File bugs at http://bugs.linaro.org For Linaro member support see http://support.linaro.org For Linaro community support email linaro-toolchain(a)lists.linaro.org -- Ryan S. Arnold | Linaro Toolchain Engineering Manager ryan.arnold(a)linaro.org | ryanarn on #linaro-tcwg @ freenode.irc.net

9 years, 3 months

1
0
0 0

[ACTIVITY] 21-25 March 2016

by Christophe Lyon

== Progress == * Validation - extended validation: updated ABE patch after review - investigating how to actually separate stdout/stderr streams in dejagnu - still seeing random results (mostly in the sanitizers tests) in the Cambridge lab * GCC - no progress on Win32-hosted toolchain bug: cannot reproduce it from a manually built toolchain - advSIMD/Neon intrinsics tests: cleanup on-going - bug 2125: forwarded upstream, quickly fixed by R.Biener, backport in progress - Misc (conf-calls, meetings, emails, ...) == Next == * Validation: - more on extended validation - random tests investigation - more on stdout/stderr * GCC: - trunk monitoring, report regressions if needed - intrinsics tests cleanup

9 years, 3 months

1
0
0 0

[ACTIVITY] Week 12

by Yvan Roux

o Easter Monday off (2/10) == Progress == o Extended validation (5/10) * Worked on benchmarking integration * Analyzed failures due to --tarbin and --check ABE's flags * Analyzed native AArch32 timeout (due to guality/GDB testcase) o Misc (3/10) * Various meetings == Plan == o Continue on extended validation o Finalize DejaGNU patches, GCC ARMv8.1 builtins fix.

9 years, 3 months

1
0
0 0

[ACTIVITY] 21 - 25 March 2016

by kugan

== Progress == * Type promotion pass (6/10) - Fixed major false positive uninit warnings = Changed tree-ssa-uinit to handle SEXT_EXPR = preserving TREE_NO_WARNING set by SRA = Somemore fixes to preserve debug loc - There are still some more but this is mainly due to how tree-ssa-uinit is designed - Working through the output patterns; some are simple changes but some needs more analysis - Planning to create a branch with the latest version for easy review * Bugs (1/10) - PR70359 * Misc (1/10) - GCC Lists * Public holiday (2/10) == Plan == * Type promotion pass benchmarking * Perf with LTO

9 years, 3 months

1
0
0 0

[Weekly] 21-25 March 2016

by Michael Collison

== This week == * Bugzilla 69663 - [ARM] Implement overflow arithmetic standard names (4/10) - Resolved all thumb2 failures - Posted new patch upstream * TCWG-247 - Create Validation Job to run on GCC Trunk Commits (1/10) - Investigation into Python API for discovering when Jenkins builders are idle * Laptop hardware failure debugging (2/10) - Requested a new laptop from Arm * Misc meeting (1/10) * Good Friday holiday (2/10) == Next week == * TCWG-247 - Create prototype implementation

9 years, 3 months

1
0
0 0

[ACTIVITY] 21 - 25 March 2016

by Prathamesh Kulkarni

== This Week == * LTO (4/10) - Committed r234490 to fix PR70366 - Spent unnecessary time tracking down known (invalid) bug PR65778 - LTO and branch out of range error: - patch to introduce max partition size param - experimenting with partition sizes to find value close to 16 mb limit. * Validation (2/10) - Pushed script to it's own repo - Reviews from Christophe on tcwg-buildapp job * Public Holidays (4/10) == Next Week == - Continue ongoing tasks

9 years, 3 months

1
0
0 0

[ACTIVITY]

by Renato Golin

== Progress == * Support (2/10) - Investigating a bit more PR16275, need some bigger changes in Clang/LLVM * Background (6/10) - Code review, meetings, discussions, general support, etc. - Planning for a bigger team (git, Jenkins, infrastructure, documentation) - Receiving new team members, planning start up tasks - Android NDK discussion, investigation Realising my activity report has been almost useless for the past month or so...

9 years, 3 months

1
0
0 0

[ACTIVITY] 20-24 March 2016

by Yao Qi

# Progress # * TCWG-532, done. [1/10] Canonicalize ARM syscall patch is committed. * TCWG-167, patch is posted for review. [4/10] Add ARM epilogue unwinder in GDB, which fixes many gdb.reverse test fails. * TCWG-545, V2 are posted. [1/10] * TCWG-547, [2/10] patches are reviewed, almost OK, but some changes are needed. * Talk with Jojo Ma. * Open tickets to install buildbot-slave on gcc compile farm for GDB buildbot setup. # Plan # * Holiday on Friday and next Monday. * TCWG-167, TCWG-545, TCWG-547. -- Yao

9 years, 3 months

1
0
0 0

[ACTIVITY] 14-18 March 2016

by kugan

== Progress == * LTO (3/10) - Read VRP algorithms * Type promotion pass (2/10) - Rebased and testing - Looking at fixing uninitilazed warning false positives * Misc (1/10) - GCC Lists - Extended validation * Public holiday (2/10) * Connect travel/recovery (2/10) == Plan == * Type promotion pass benchmarking * Perf with LTO * VRP

9 years, 3 months

1
0
0 0

[ANNOUNCE] Linaro Binary Toolchain Release GCC 5.3-2016.02 [Corrected Links]

by Ryan Arnold

The Linaro Binary Toolchain ============================ The Linaro GCC 5.3-2016.02 Release is now available. Notice: All Linaro GCC 5 series toolchain users should migrate to the latest version of the Linaro GCC 5 toolchain in order to mitigate potential security exposure to CVE-2015-7545. See the NEWS section below for details. Download release packages from: http://releases.linaro.org/components/toolchain/gcc-linaro/5.3-2016.02/ http://releases.linaro.org/components/toolchain/binaries/5.3-2016.02/ Previous snapshots and release-candidates are at: http://snapshots.linaro.org/components/toolchain/binaries/ Previous releases are at: http://releases.linaro.org/components/toolchain/binaries/ Host Requirements ================== Linaro officially supports the current and previous Ubuntu LTS releases (as of the time of this release). This does not mean that the toolchain will not work on other/older Linux distributions. See the following for the life-time of Ubuntu LTS releases. https://wiki.ubuntu.com/Releases The host system upon which the cross-compiler will run requires a minimum of glibc 2.14, because of API changes to glibc's memcpy API. https://bugs.linaro.org/show_bug.cgi?id=1869 Package Versions ================= Linaro GCC 5.3-2016.02 FSF glibc 2.21 (release/2.21) Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch) Linaro binutils 2.25 (linaro_binutils-2_25-branch) FSF GDB 7.10 (gdb-7.10-branch) Linaro toolchain package git branches are hosted at: http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search NEWS for Linaro GCC 5.3-2016.02 ================================ * Applied fix for CVE-2015-7545 - A stack-based buffer overflow in glibc's getaddrinfo() was corrected in glibc 2.23 and backported into glibc 2.21. https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html * ARMv8.1 Instruction Support - ARMv8.1 instructions support was checked into GCC and binutils. It has been backported into Linaro GCC 5.3 and Linaro binutils 2.25. * Backported -Bsymbolic-functions into Linaro binutils 2.25. * Performance related backports from Linaro GCC 5.2-2015.11, Linaro GCC 5.2-2015.12, and Linaro GCC 5.3-2016.01-1 have been included. See the following Linaro GCC snapshots: http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.2-2015.11/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2015.12/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.01-1/ Contact Linaro =============== File bugs at http://bugs.linaro.org For Linaro member support see http://support.linaro.org For Linaro community support email linaro-toolchain(a)lists.linaro.org

9 years, 3 months

1
0
0 0

[ANNOUNCE] Linaro Binary Toolchain Release GCC 5.3-2016.02

by Ryan Arnold

The Linaro Binary Toolchain ============================ The Linaro GCC 5.3-2016.02 Release is now available. Notice: All Linaro GCC 5 series toolchain users should migrate to the latest version of the Linaro GCC 5 toolchain in order to mitigate potential security exposure to CVE-2015-7545. See the NEWS section below for details. Download release packages from: http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.02/ http://snapshots.linaro.org/components/toolchain/binaries/5.3-2016.02/ Previous snapshots and release-candidates are at: http://snapshots.linaro.org/components/toolchain/binaries/ Previous releases are at: http://releases.linaro.org/components/toolchain/binaries/ Host Requirements ================== Linaro officially supports the current and previous Ubuntu LTS releases (as of the time of this release). This does not mean that the toolchain will not work on other/older Linux distributions. See the following for the life-time of Ubuntu LTS releases. https://wiki.ubuntu.com/Releases The host system upon which the cross-compiler will run requires a minimum of glibc 2.14, because of API changes to glibc's memcpy API. https://bugs.linaro.org/show_bug.cgi?id=1869 Package Versions ================= Linaro GCC 5.3-2016.02 FSF glibc 2.21 (release/2.21) Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch) Linaro binutils 2.25 (linaro_binutils-2_25-branch) FSF GDB 7.10 (gdb-7.10-branch) Linaro toolchain package git branches are hosted at: http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search NEWS for Linaro GCC 5.3-2016.02 ================================ * Applied fix for CVE-2015-7545 - A stack-based buffer overflow in glibc's getaddrinfo() was corrected in glibc 2.23 and backported into glibc 2.21. https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html * ARMv8.1 Instruction Support - ARMv8.1 instructions support was checked into GCC and binutils. It has been backported into Linaro GCC 5.3 and Linaro binutils 2.25. * Backported -Bsymbolic-functions into Linaro binutils 2.25. * Performance related backports from Linaro GCC 5.2-2015.11, Linaro GCC 5.2-2015.12, and Linaro GCC 5.3-2016.01-1 have been included. See the following Linaro GCC snapshots: http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.2-2015.11/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2015.12/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.01-1/ Contact Linaro =============== File bugs at http://bugs.linaro.org For Linaro member support see http://support.linaro.org For Linaro community support email linaro-toolchain(a)lists.linaro.org -- Ryan S. Arnold Linaro Toolchain Working Group - Engineering Manager www.linaro.org

9 years, 3 months

1
0
0 0

[ACTIVITY] 14-18 March 2016

by Christophe Lyon

== Progress == * Validation - extended validation: submitted ABE patch for discussion - noticed random results on some tests in the Cambridge lab. maybe caused by excessive load on the tester, or stdout/stderr problems - investigating how to actually separate stdout/stderr streams in dejagnu * GCC: - branch merge review for 2016.03 snapshot - AdvSIMD/Neon intrinsics tests: more cleanup, wondering about poly128_t prototypes * Misc (conf calls, meetings, emails, ....) == Next == * Validation: - more on extended validation - random tests investigation - more on stdout/stderr * GCC: - trunk monitoring, report regressions if needed - intrinsics tests cleanup

9 years, 3 months

1
0
0 0

[ACTIVITY] 14-18 March 2016

by Prathamesh Kulkarni

== This Week == * LTO (3/10) a) section anchors: - prototype patch to bind functions to global vars - looked at balanced partitioning b) chromium LTO build fails with ICE on trunk for arm-linux-gnueabihf: http://pastebin.com/sX6yKLBP c) ipa-comdat - Looked at the pass. - trying to address TODO: put symbol in it's own comdat section * Validation (1/10) - prototype job in bash. * Holidays (6/10) == Next Week == Continue ongoing tasks

9 years, 3 months

2
1
0 0

[ACTIVITY] Week 11

by Yvan Roux

== Progress == o 2016.03 Snapshot (2/10) * Reviewed pending backports * Merged FSF GCC 5 branch * Released 2016.03 snapshot o Extended validation (2/10) * Native validation deployed * Testing/Fixing Native Trigger job o GCC dev. (3/10) * Remote validation sanitizing: - continued discussion on output pattern - discuss I/O conflict patch with Rob, preparing a new patch * Bug #2125 - asm inline support * ARMv8.1 __sync builtins fix: on-going o Misc (3/10) * Various meetings == Plan == o Extended validation, DejaGNU patches, GCC ARMv8.1 builtins fix

9 years, 3 months

1
0
0 0

[ACTIVITY] Monday 14th - Friday 18th March

by Bernie Ogden

Port to microinstance - TCWG-432 [5/10] * Non-lab side of minimal trust benchmarking * More investigation of runtime anomalies * Reordered builder phases to do useful work while waiting for targets * Updated everything to work with benchmarking LAVA user (rather than running as me) Automated backport benchmarking - TCWG-352 [2/10] * Cycles of review/development/testing Controlled image builds - TCWG-360 [1/10] * More failures to get image to boot on Juno Log critical data - TCWG-349 [1/10] * Everything now logged, except where it depends on TCWG-360 Misc - [1/10] =Plan= Finish non-lab side of minimal trust benchmarking Commit backport benchmarking, review permitting Tweak microinstance in reaction to lab work More Juno image work More runtime anomaly work =Availability= Off from this Friday, back for three days from Monday 4th April Return to ARM on Thursday 7th April

9 years, 3 months

1
0
0 0

[Weekly] 14-18 March 2016

by Michael Collison

== This week == * Bugzilla 69663 - [ARM] Implement overflow arithmetic standard names (5/10) - Resolved 50% of thumb2 failures - Resolved issues with overlapping registers and not setting condition codes - Wrote compile only test cases that pass validation * TCWG-247 - Create Validation Job to run on GCC Trunk Commits (2/10) - Investigation into Python API for discovering when Jenkins builders are idle * Linaro connect recovery day (2/10) * Misc meeting (1/10) == Next week == * Bugzilla 69663 - [ARM] Implement overflow arithmetic standard names - Resolve remaining thumb2 issues * TCWG-247 - Create prototype implementation

9 years, 3 months

1
0
0 0

[ACTIVITY]

by Renato Golin

= Progress == * Day off (2/10) - After Connect, recuperating, jet lagging * EuroLLVM (6/10) - Flying Wed to Barcelona, attending conference - Back on Saturday * Background (2/10) - Code review, meetings, discussions, general support, etc. - Planning for a bigger team (git, Jenkins, infrastructure)

9 years, 3 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain