Re: [hpc-sig-devel] Re: [FYI] HCQC(HPC compiler quality checker) on GitHub

On 8 November 2017 at 17:30, Luis Machado wrote: > FTR, i don't see any attached PDF's in this e-mail either. It's possible that the pdf went to hpc-sig-dev and not toolchain. maybe toolchain doesn't allow attachments? ___

Re: [hpc-sig-devel] Re: [FYI] HCQC(HPC compiler quality checker) on GitHub

On 8 November 2017 at 17:19, Masaki Arai wrote: > Hi, > > I am sorry for the inconvenience. > > #I'm not sure what is going on. > #I can extract PDF from my first e-mail.!? I could see the PDF on the first email, and on this one too. :) --renato

Re: [hpc-sig-devel] GCC extensions for `hcqc'

On 29 August 2017 at 10:15, Masaki Arai wrote: > Thank you very much for your comments and advice. > I checked the URL． > If there is no objection, I will consider proposing this function(and > alternative > appraoch) on the GCC mailing list (after

Re: [hpc-sig-devel] GCC extensions for `hcqc'

+linaro-toolchain, hoping to get more eyes into it. cheers, --renato On 25 August 2017 at 17:59, Masaki Arai wrote: > Hi, > > I extended GCC 7.1(or GCC 7.2) for `hcqc'. > I would be grateful if you could give me a comment about whether > this extension is acceptable and

Re: Q: reasons for lack of support for C++ in OP-TEE?

On 14 August 2017 at 10:27, Peter Smith wrote: > Perhaps the most difficult decision is whether to support exceptions. > For your own code, choosing not to support exceptions isn't a problem > as both gcc and clang can compile without exception tables, however > many C++

Re: [ACTIVITY] 31 Oct -- 04 Nov

On 4 November 2016 at 10:56, Peter Smith wrote: > [TCWG-901] Investigate lld as a system linker > With downstream fixes, using lld as the system linker on a Chromebook I can : > - Build llvm, lld and run the regression tests successfully > - Use lld as the linker in the

Sanitiser 48-VMA Support

Hi Christophe, Here are the commits, in order, that Adhemerval did to support 48-bit VMA on AArch64. r275792: [asan] Enable 48-bit VMA support on aarch64 r277137: tsan: Enable 48-bit VMA support on aarch64 r279752: msan: Enable 48-bit VMA support on aarch64 r279753: dfsan: Enable 48-bit VMA

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

On 3 June 2016 at 21:02, Rui Ueyama wrote: >> Is the LLD community in agreement that a few core developers can and >> will continue to block contributions, while doing all the work >> themselves until such a day that it's deemed ready by the same >> developers, in which time that

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

On 3 June 2016 at 18:47, Rui Ueyama wrote: > Renato, it is not appropriate to call it my and Rafael's pet project. Hi Rui, I apologise, that was wrong in all levels. I know how much other people have contributed, but these people are on the inside already, so their

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

On 3 June 2016 at 17:10, Rafael Espíndola wrote: > Do keep in mind you are comparing a 11 year old project and a 11 month > old one. There is a lot more churn on the 11 month old one. LLD is at least 5 years old. Every time you re-write it doesn't reset history. >

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

On 3 June 2016 at 01:53, Rui Ueyama wrote: > Not so fast to conclude that the community is not trustworthy, it doesn't > consist of a single person or a single action. This is not an isolated incident. This seems to be the general behaviour around LLD, which is less so in the

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

On 2 June 2016 at 23:22, Rafael Espíndola 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

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

On 2 June 2016 at 20:49, Rafael Espindola via llvm-commits wrote: > Author: rafael > Date: Thu Jun 2 14:49:53 2016 > New Revision: 271569 > > URL: http://llvm.org/viewvc/llvm-project?rev=271569=rev > Log: > Start adding tlsdesc support for aarch64. > > This is mostly

Re: missing gold --be8 support

On 24 May 2016 at 18:13, Peter Smith wrote: > I think that the bit missing from Gold is the endian reversal code for > instructions, in ARMv7 BE8. If that is implemented then no additional > support is needed for LTO. I would suspect that it would be much > quicker to

Re: missing gold --be8 support

On 24 May 2016 at 17:05, Jim Wilson wrote: > 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? Hi Jim,

[ACTIVITY]

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

[ACTIVITY]

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

[ACTIVITY]

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

Re: Updating LLVM on Debian/Ubuntu

On 13 March 2016 at 18:42, Matthias Klose wrote: > except for the LTS releases, which have a two year release cycle. 16.04 LTS > will be the next LTS. Damn it. > As announced on debian-devel-announce, the freeze will be in Feb 2017. Ok, less problematic in Debian's case. >

Updating LLVM on Debian/Ubuntu

Hey, Regarding the GCC ABI 5 issue, I was wondering what's the policy behind updating packages on stable updates for both Debian and Ubuntu. Our time frame is a bit constrained, and we definitely will have to take some hard decisions in the next six months, so I'd like to understand everything

FreeBSD + LLD Update

FYI, http://lists.llvm.org/pipermail/llvm-dev/2016-March/096449.html cheers, --renato ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain

Re: gcc 5.2 code quality

On 2 March 2016 at 14:36, Edward Nevill wrote: > It is doing cmp x2, 8 then a few instructions later, without modifying > x2/w2 and without any intervening branch destinations it does cmp w2, 8. > I assert the 2nd cmp w2, 8 and bls are redundant, because we know it is >

[ACTIVITY]

== Progress == * Support (4/10) - Updating patch D17141 for Darwin, resubmitting, discussions. - Understanding PR21778, may need changes to SLP - Benchmarking some scheduler choices for A17 * Release (1/10) - 3.8.0 RC3 validation * Background (5/10) - Code review, meetings, discussions,

[ACTIVITY]

== Progress == * Conference (2/10) - More EuroLLVM paper reviews, discussions * Support (5/10) - Looking at PR16275 (review D17141) * Background (3/10) - Code review, meetings, discussions, general support, etc. - Buildbots broken, bisects, debugging - Defining and posting Job ad (wanna

[ACTIVITY]

== Progress == * Conferences (4/10) - Fosdem organisation, travel, video cutting (all lost) - EuroLLVM paper review, schedule, meetings * Buildbots (2/10) - Bisecting test-suite regression - Infrastructure clean up - Reverting broken patches * Support (1/10) - Looking at some bugs, fixed

[ACTIVITY]

== Progress == * Buildbots (2/10) - Installing bisect tool on ARM and AArch64 bots - SVN access broken in Austin - Investigating failures on AArch64-only bots * Release (2/10) - Running 3.8.0 benchmarks * Planning (2/10) - Finalising the roadmap for 2016/17 * Conferences (2/10) - Final

[ACTIVITY]

== Progress == * Support (5/10) - Bug triage: reviewing the 300+ bugs on ARM - remaining 220 bugs are all still pertinent * Release (2/10) - Woes due to GCC ABI change may delay 3.8.0 release - Tested on both ARM and AArch64 with old environment, all green. * Background (3/10) - Code

GCC's ABI 5

Folks, I'd like to know the general opinion on this: https://llvm.org/bugs/show_bug.cgi?id=23529 From past experience, and my limited point of view, it seems that the GCC community decided to change the ABI, plotted some runes, conjured up a broken implementation (whose bugs people will exploit

[ACTIVITY]

== Progress == * Support (5/10) - Bug triage: reviewing the 300+ bugs on ARM - closing fixed ones (+35) - adding deps for meta bugs (kernel, android, ias, chromium) (~15) - moving to ARM/AArch64 components, etc. (~30) - Checking a few more kernel patches for Clang support with Arnd *

[ACTIVITY]

== Progress == * Support (2/10) - Having a go at PR25722, too hacky for a feature that can be easily worked around. - Reviewing some kernel issues with Arnd * Planning (6/10) - Drafting 2 year plans for LLVM * Background (2/10) - Code review, meetings, discussions, general support, etc.

Re: Linaro LLVM engagement

tions and overall usage are completely different. > 4. Certain links (e.g Roadmap) at > https://wiki.linaro.org/WorkingGroups/ToolChain/LLVM > ask for login credentials. Any comment on how to obtain the permission? > > You will need to ask either to Ryan Arnold <ryan.arn...@linaro.o

[ACTIVITY]

== Progress == * Holiday (2/10) * Release (1/20) - 3.7.1 Final, all green * Maintenance (5/10) - Fixing PR25720 - Bug cleaning: PR18921, PR13259, PR13138, PR12926, PR17963, PR18187, PR22692 - Checked strided vectorizer on ToT, EEMBC 2x geomean! * Background (2/10) - Code

[ACTIVITY]

== Progress == * Ill (4/10) * Support (1/10) - Bugzilla issues (PR20490, PR24635, PR24350, PR20025, PR25720, PR25722) * Benchmarks (1/10) - Checking some previous benchmark results on A57 * Buildbots (2/10) - Getting AArch64 full bot back to rotation, since it's stable now - Re-enabling

[ACTIVITY]

== Progress == * Support (6/10) - Trying to add ADRL support in the assembler: http://llvm.org/PR24350 * Buildbots (1/10) - Some breakages, nothing serious * Background (3/10) - Code review, meetings, discussions, general support, etc. - Working on 2016's plan

[ACTIVITY]

== Progress == * Buildbots (1/10) - Bisecting breakages, testing ASAN patches * Release (1/10) - Testing 3.7.1-RC1, all green * Benchmarks (3/10) - Updating some benchmarks results, running EEMBC on HiKey - Investigating old performance reports * Background (5/10) - Code review, meetings,

Re: Configuration question

On 17 November 2015 at 22:10, Pinski, Andrew wrote: > Or better yet use ifunc directly to check on them. I was going to say, this looks like the kind of thing IFUNC was designed for. :) --renato ___ linaro-toolchain

[ACTIVITY]

== Progress == * Buildbots (4/10) - Found culprit for self-hosting breakages - Bot didn't get right because of dirty builds - Moving all self-hosting bots to clean builds (~3h) - More work on MIPS patch breaking self-hosting - Several breakages and bisections - Adding first cloud

[ACTIVITY]

== Progress == * Buildbots (5/10) - Some broken bots, bisecting, etc - Helping a MIPS patch pass on ARM bot * Maintenance (2/10) - SciMark2 seems not to be unstable or slow any more in ARM64 - Some more investigations on Loop Load Elimination - Profiling bigfib on APM and HiKey *

[ACTIVITY]

== Progress == * Infrastructure (4/10) - Installing Ubuntu on APM (perf works!) - Setting up a HiKey for in-order perf - Helping Milosz with crashing HiKeys * Maintenance (4/10) - Helping ARM with test-suite patches (D14061) - Investigating read-after-read dependency (D13259) * Background

[ACTIVITY]

== Progress == * Maintenance (5/10) - Investigating some LivermoreLoops that don't vectorise - Reducing cases to single specific causes * Background (5/10) - Code review, meetings, discussions, general support, etc. - More code of conduct stuff, license change to Apache 2 - Following up on

[ACTIVITY]

== Progress == * Libraries (3/10) - Back investigating libc++ issues in AArch64 buildbot - http://buildmaster.tcwglab.linaro.org/builders/clang-cmake-aarch64-prototype - Trying to solve the rt/unw/c++ library entanglement in the driver * Buildbots (1/10) - Trying to perf an application on

[ACTIVITY]

== Progress == * Maintenance (1/10) - Removed redundant DefaultCPU in ARMTargetInfo * Buildbots (4/10) - Looong discussions upstream about stability of buildbots - Trial with IFC6410 marginally successfull, still not good enough, aborting - Moved benchmark buildbot to silent (avoid

[ACTIVITY]

== Progress == * Buildbot (2/10) - Investigating sanitizer crash in AArch64 - Found: 247264, reverted 247674 - Other sanitizer crashes * Maintenance (4/10) - More VMA investigations, discussions - More TargetTuple discussions - Investigating BLX bug on ARMv4 (PR24858) * Background

[ACTIVITY]

== Progress == * Libraries (1/10) - Working on getting the libc++ tests green * Maintenance (6/10) - Working with Vinicius on the gnueabi memcpy issue - More TargetTuple/TargetParser discussions - More sanitizers discussions, patch reviews * Background (3/10) - Code review, meetings,

[ACTIVITY]

== Progress == * Holidays (4/10) * Buildbots (2/10) - Several breakages, Clang alignment issue sill breaking self-hosted bots... * Maintenance (2/10) - Backtracks on the TargetParser, code heavily modified, discussions ensued. - Helping Vinicius with __aeabi_memcpy in the kernel *

[ACTIVTY]

== Progress == * Maintenance (CARD-1833 2/10) - Fixing libc++abi build on AArch64 - Trying to remove a hack in ARMTargetInfo about default CPUs - Bisecting PR24292 - Working with ARM to fix it, backport * Buildbots (CARD-1823 8/10) - Working with Adhemerval on VMA 42bits sanitizer -

[ACTIVITY]

== Progress == * Buildbots (CARD-1823 6/10) - Setting up new APMs - Running around for a decent UEFI, Kernel, Distro - Testing different builds, configurations - Managed to get one APM doing the test-suite *only*! sigh... -

[ACTIVITY]

== Progress == * Performance (CARD-1832 3/10) - Profiling SPEC2k mesa, found some issues - Investigating r232513, unlikely the culprit, but interesting case * Releases (CARD-1431 1/10) - Spinning 3.7.0 RC2 * Buildbots (CARD-1823 4/10) - Setting up new APMs - Dealing with ASAN/TSAN bot

[ACTIVITY]

== Progress == * Performance (CARD-1832 1/10) - Checking differences of PostRAListSched on OOO ARM cores - Not many changes, ignoring for now * Maintenance (CARD-1833 4/10) - Building libc++/abi/unwind in LLVM/Clang tree - Getting -Wa,-mfpu patches in, last important Clang driver ARM bug

[ACTIVITY]

== Progress == * Maintenance (CARD-1833 4/10) - Clang driver: - Passing -Wa,-mfpu and friends to assembler (D11147, D11148) - Passing -I to assembler (D11185) - Don't include libgcc/asm if using libunwind/libc++abi (D11153) - Asm warnings: - Trying again to look for a way to disable asm

[ACTIVITY]

== Progress == * Releases (CARD-1431 1/10) - Released 3.6.2-final * Maintenance (CARD-1833 5/10) - Reducing runtime of some benchmarks in LLVM's test-suite by getting rid of millions of useless fprintf calls. - Working on https://llvm.org/PR20700 some more * Background (4/10) - Code

[ACTIVITY]

== Progress == * Maintenance (CARD-1833 4/10) - ADD/SUB with negative immediates solved by a year old patch from ARM, sigh. On to the next bug... :( - Working on https://llvm.org/PR20700 * Buildbots (CARD-1823 2/10) - Moving benchmark bot to CMake, fixing deepcopy bug in environment

[ACTIVITY]

== Progress == * Maintenance (CARD-1833 4/10) - Found the trail on the ADD/SUB with negative immediate - Submitting RFC for discussion (http://llvm.org/PR20978) - Bugzilla farming - More LNT investigations (http://llvm.org/perf/ unstable) * Releases (CARD-1431 1/10) - Building, testing and

Re: [TCWG] clang/llvm build - tips and advices

On 24 June 2015 at 14:50, Adhemerval Zanella adhemerval.zane...@linaro.org wrote: I tried some of author advices getting very good results. Basically I moved to optimized clang build, changed to gold linker and used another memory allocator than system glibc one. Results in build time for all

[ACTIVITY]

== Progress == * Maintenance (CARD-1833 1/10) - Looking at AArch64 ADD-SUB a bit more * Buildbots (CARD-1823 6/10) - Moving LNT bot to CMake - Setting up LLD and LLDB buildbots - Investigating LNT instability / Perf buildbot * Background (3/10) - Code review, meetings, discussions, etc. -

[ACTIVITY]

== Progress == * Maintenance (CARD-1833 2/10) - Initial work on ADD-SUB for negative imm in asm * Buildbots (CARD-1823 6/10) - Adding test-suite to CMake buildbot (D10244) - Bisecting broken self-hosting vfp3 bots * Background (2/10) - Code review, meetings, discussions, etc. - Some more

[ACTIVITY]

== Progress == * Releases (CARD-1431 1/10) - Final ARM/AArch64 3.6.1 * Automation Framework (CARD-1378 1/10) - More meetings with Lab about infrastructure * Maintenance (CARD-1833 5/10) - Working on FIXMEs to TargetParser * Buildbots (CARD-1823 1/10) - Bisecting self-hosting failure on

[ACTIVITY]

== Progress == * Releases (CARD-1431 4/10) - Testing 3.6.1 on ARM, green - Re-flashing LLVM APM due to crash - Testing 3.6.1 on AArch64, green * Maintenance (CARD-1833 2/10) - Fixing enum vs. macro conflicts (PR23482) - Working on FIXMEs to TargetParser (Triple) * Background (4/10) - Code

[ACTIVITY]

== Progress == * Public holiday on Monday (2/10) * Automation Framework (CARD-1378 1/10) - Debugging / Setting up VPN to the lab - Investigating APM crash * Releases (CARD-1431 1/10) - Reviewing patches for 3.6.1, some failures * Maintenance (CARD-1833 3/10) - Unifying ARM target parser *

[ACTIVITY]

== Progress == * Automation Framework (CARD-1378 2/10) - Interface with the lab/system teams (plan, schedule) - Saving the bridge's image into an SD card * Maintenance (CARD-1833 6/10) - Unifying target parser (PR20787 / D9435) * Background (2/10) - Code review, meetings, discussions, etc.

[ACTIVITY]

== Progress == Friday holiday * Automation Framework (CARD-1378 2/10) - Power cut in the office - Fixing gateway, rebooting machines - Mob management * LLVM ARM Maintenance (CARD-1833 2/10) - ARMTargetParser review * Background (4/10) - Code review, meetings, discussions, etc. - All

[ACTIVITY]

== Progress == * Automation Framework (CARD-1378 5/10) - Moving LLVM lab into llvm.tcwglab subnet - Passing down my knowledge to the lab team - Helping them set up the new builders * Background (5/10) - Code review, meetings, discussions, etc. - Upgrading APM's compiler/binutils - Writing

[ACTIVITY]

== Progress == * Thursday off (2/10) * Buildbots (CARD-1823 1/10) - Fixing llvm-apm-01 (disk problem) - Fixing llvm-d01-04 (my bad) * Releases (CARD-1431 1/10) - Spinning release 3.5.2 RC1, all green * Automation Framework (CARD-1378 3/10) - A lot of time wasted in infra shenanigans *

Re: [ACTIVITY] 9 - 13 March 2015

On 17 March 2015 at 00:42, Omair Javaid omair.jav...@linaro.org wrote: -- Written wiki pages for LLDB developer process [1/10] Where? We need to move it here: https://collaborate.linaro.org/display/LLVM/LLVM@Linaro cheers, --renato ___

Re: [ACTIVITY] 9 - 13 March 2015

at 15:13, Renato Golin renato.go...@linaro.org wrote: On 17 March 2015 at 00:42, Omair Javaid omair.jav...@linaro.org wrote: -- Written wiki pages for LLDB developer process [1/10] Where? We need to move it here: https://collaborate.linaro.org/display/LLVM/LLVM@Linaro cheers

[ACTIVITY]

== Progress == * Automation Framework (CARD-1378 5/10) - Setting up new servers * Background (5/10) - Code review, meetings, discussions, etc. - Updating some LLVM dev scripts - Adding tools checks to LNT - EuroLLVM Paper selection - LLDB/ARM meetings - Bisecting lots of failures in all

[ACTIVITY] Week 8

== Progress == * Releases (CARD-1431 2/10) - Spinning RC4, final, all green * Buildbots (CARD-1823 1/10) - Adding new quick Thumb2 non-NEON bot - Adding new full self-hosting Thumb2 bot * Libraries (CARD-1831 1/10) - Trying to build a soft-float compiler-rt test-suite * Sanitizers for

[ACTIVITY] Week 6

== Progress == * Automation Framework (CARD-1378 1/10) - Restarting build-02 - Trying new way to setup juno-01, failed - Moving gateway-config to new private git server * Release 3.6 (CARD-1431 4/10) - Found NEON regression, reverting patches - Setting up more new NEON buildbots *

[ACTIVITY] Week 5

== Progress == * Automation Framework (CARD-1378 1/10) - Setting up new box * Release 3.6 (CARD-1431 5/10) - Looking for the patch that introduced a major NEON regression since December * Background (4/10) - Code review, meetings, discussions, etc. - More Jira farming... - Some EuroLLVM

[ACTIVITY] Week 4

== Progress == * Automation Framework (CARD-1378 2/10) - Rebooting machines, again... - Fiddling with bugzilla, wiki * Release 3.6 (TCWG-575 5/10) - Investigating ARMv7 bootstrapping failures - Rebuilding manually with cmake, as autoconf build is bogus - Turns out wasn't autoconf, but a

[ACTIVITY] Week 3

== Progress == * Tuesday sick * Automation Framework (CARD-1378 5/8) - Fixing more crashed Junos - Working on QEMU VMs on gateway (buildbot master, nagios) - Finalising server purchase, building new rack * Release 3.6 (TCWG-575 1/8) - AArch64 built and tested, all green. - ARM is broken,

[ACTIVITY] Week 2

== Progress == * Automation Framework (CARD-1378 2/10) - DNS requests (Hetzner, bridge), new APM - Following up on purchase of new server, new rack, UPS * Buildbots (TCWG-76 4/10) - Enabling swap on dragon boards (local bots) - Investigating AArch64 RT failure, XFAIL like ARM - AARch64 full

[ACTIVITY] Week 1

== Progress == 1 day week: * Automation Framework (CARD-1378 1/2) - Resetting APMs and Junos that fell during the holidays * Release 3.5.1 (TCWG-477 1/2) - Testing RC2, all good == Plan == * improve buildbots (swap, verbose, libs) * fix libc++abi NEON/VFPv3 unwinder * purchase new builder,

[ACTIVITY] Week 51

== Progress == * Friday off * Automation Framework (CARD-1378 2/8) - Writing up best practices, lab structure, etc - Removing port forwards, private keys from the lab - IT ticket to remove tcwg-sysadmin from public git * Toolchain (CARD-862 1/8) - Fixed compiler-rt problem on AArch64 build

[ACTIVITY] Week 50

== Progress == * Automation Framework (CARD-1378 5/10) - Getting around fastboot issues on Dragon - Upgrading Dragons to 3.17 / utopic - Testing stability of Dragon boards once again - Writing best practices, and lab setup documents - Liaising with ST and Qualcomm to stress their boards *

IFC6410 for toolchain testing

Folks, Me and Nick have been back and forth with the IFC6410, using Linaro's utopic Ubuntu + 3.17 kernel, and I can now declare it stable enough to run toolchain tests, maybe not yet builds. The reason is that the kernel, although stable, is only just because it throttles speed to a minimum.

Re: IFC6410 for toolchain testing

On 11 December 2014 at 14:36, Nicolas Dechesne nicolas.deche...@linaro.org wrote: and it's quite consistent over multiple runs. So it's much more than 40% actually.. if we apply these ratios we get theoretical numbers that makes more sense... the ifc6410 should definitely be faster than

[ACTIVITY] Week 49

== Progress == * Automation Framework (CARD-1378 5/8) - Re-adding Junos and D01s to the rack - Planning access from remote servers - Following up new rack setup - Moving lab bridge to a VM - Re-checking all boards for stability - Working on the dragon boards to get them stable * Background

[ACTIVITY] Week 48

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

[ACTIVITY] Week 47

== Progress == Lab move (for the last 11 days non-stop) == Plan == Sleep ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ACTIVITY] Week 46

== Progress == Lab move == Plan == Lab move ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ACTIVITY] Week 45

== Progress == * Automation Framework (CARD-1378 4/8) - Moving TCWG machines to the new office - Setting up new rack, stacking boards, etc. - Setting up Junos * Buildbots (TCWG-76 2/8) - Moving buildbots to the new office - Checking libcxxabi failure, marking as XFAIL - All bots green *

[ACTIVITY] Week 44

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

[ACTIVITY] Week 43

== Progress == * Automation Framework (CARD-1378 1/10) - Setting up Junos with ARM * Toolchain (CARD-862 1/10) - Some progress on fpu parser issue - Produced a lot more work for the near future * Buildbots (TCWG-76 4/10) - Setting up a libc++ buildbot, working on reducing failures - Some

[ACTIVITY] Week 41

== Progress == * Automation Framework (CARD-1378 1/10) - Planning LAVA server for new TCWG gateway * Buildbots (TCWG-76 7/10) - Fixing Compiler-RT buildbot (from 69 to 4 failures) * Background (2/10) - Code review, meetings, discussions, etc. - Re-testing a change in inst combine that broke

[ACTIVITY] Week 40

== Progress == * Automation Framework (CARD-1378 5/10) - Broken Chromebooks in the lab - Setting up AMD machine - Setting up Juno boards * Background (5/10) - Code review, meetings, discussions, etc. - Writing LPC presentations - Broken buildbots == Plan == * Spend less time fiddling

[ACTIVITY] Week 36

== Progress == * Automation Framework (CARD-1378 2/10) - Configuring D01s into a three-schroot box - Turned out unstable, reverting to 4-core setup * Toolchain (CARD-862 0/10) - Re-committed vectorizer patch with MSVC2012-friendly code * LLVM 3.5 Release (TCWG-476 1/10) - Final release out,

LLVM 3.5.0 Release

Folks, Clang+LLVM 3.5.0 was released yesterday (3rd Sep) and Linaro, as usual, have tested both ARM and AArch64 native builds. This is a major milestone for LLVM on ARM/AArch64, please read the release notes to find out more. http://llvm.org/releases/3.5.0/docs/ReleaseNotes.html You can

[ACTIVITY] Week 35

Public holiday + personal holiday (2 days) * Toolchain (CARD-862 0/10) - Proposing change on assembler behaviour (PR20757) * LLVM 3.5 Release (TCWG-476 1/6) - Another critical bug found, rolling RC4 * Background (5/6) - Code review, meetings, discussions, etc. - Presentations (Connect, LPC)

[ACTIVITY] Week 34

== Progress == * Automation Framework (CARD-1378 2/10) - Changing D01s to 16 cores with taskset + schroot * LLVM 3.5 Release (TCWG-476 2/10) - Broken compiler-rt div/mod backported to 3.5 rc3 - Tested and released RC3 (possibly the last) * Toolchain (CARD-862 2/10) - Found problems with

[ACTIVITY] Week 33

== Progress == * Benchmarks (CARD-716 2/10) - Wrapping up SPEC run, some results - Fix missing tests, running with -ffast-math * Toolchain (CARD-862 4/10) - A few more assembler fixes - http://llvm.org/PR20462 - http://llvm.org/PR20595 - Some vectorizer cleanups -

[ACTIVITY] Week 32

* Benchmarks (CARD-716 3/10) - Working on Linaro's SPEC scripts for LLVM - Running SPEC2000 INT/FP (C/C++ only) on both ARMv7 and AArch64 - Re-writing some EEMBC scripts to be more stable - EEMBC reported some regressions from 3.4.2 - But still same when compared with GCC 4.8 (all in Jira) *

Re: No arm-eabi builds on latest Linaro Android 4.9 toolchain?

On 1 August 2014 04:01, 박주형 qkrwngud...@gmail.com wrote: TL;DR, I need arm-eabi builds from Linaro Android toolchains. arm-none-eabi builds are not built with linker plugin enabled. I may be wrong, but I think the Android folks build their own compiler. Have you checked with them? cheers,

[ACTIVITY] Week 31

== Progress == * Toolchain (CARD-862 2/10) - Helping debug some sanitizer work - Re-evaluating compiler-rt on ARM with CMake * LLVM 3.5 Release (TCWG-476 2/10) - Working on SPEC to run with LLVM * Background (6/10) - Code review, meetings, discussions, patches, etc. - Email and patch

Re: [ACTIVITY] Week 30

On 28 July 2014 14:27, Christopher Covington c...@codeaurora.org wrote: - Work around the lack of perf on v8? Out of curiosity, what exactly is missing? Hi Christopher, As far as I know, everything. But maybe this is just for the hardware we have in the lab... Do you guys have perf working

[ACTIVITY] Week 30

== Progress == * GNU Cauldron (4/10) - GCC+LLVM presentation had some positive reviews - Discussed sanitizers roadmap - Very interesting meeting with QuIC * TCWG Sprint (4/10) - Mostly about GNU tools - Team Mission streamlined, looking good - LLVM roadmap attracted some attention - We

[ACTIVITY] Week 28

== Progress == * Monday holiday * Automation Framework (CARD-1378 6/8) - TCWG D01 moved in, Chromebooks out - Movng LLVM buildbots to D01s - D01s have no NEON support... :S - We might have to move some Chromes back in - Moving hackboxes to Chromebook 2s * Background (2/8) - Code

[ACTIVITY] Week 26

== Progress == * Toolchain (CARD-862 1/10) - Testing Compiler-RT on autoconf/ARM - Checking LLD * Automation Framework (CARD-1378 6/10) - Writing script to manage TCWG rack - Testing D01 with new kernel - Testing Chromebook 2 vs. 1 vs. D01 for LLVM - Cleaning up failed Chromebooks -

[ACTIVITY] Week 25

== Progress == * Automation Framework (CARD-1378 8/10) - Setting up D01s - Wasting time on Pandas - Setting up serial console - Preparing Chromebook2s - Testing remote gcc check * Background (2/10) - Code review, meetings, discussions, etc. == Plan == * help Guodong with D01

[ACTIVITY] Week 24

== Progress == * Kernel (CARD-1246 1/10) - Helping LLVMLinux to test in LAVA * Background (9/10) - Code review, meetings, discussions, etc. - Setting up Chromebooks again (up, crouton) - Setting up APM boards (up) - Setting up D01 boards (bricked 2) == Plan == * work with guodong, fabo,

  1   2   >