linaro-toolchain

linaro-toolchain@lists.linaro.org

14 participants
5701 discussions

Please use staging for your new bots; clang-cmake-aarch64-full is red for a month

by Galina Kistanova

Hello Linaro Toolchain Working Group, Please connect your new bots to the staging first and make them reliably green there: linaro-aarch64-flang-debug linaro-aarch64-flang-latest-clang linaro-aarch64-flang-latest-gcc clang-cmake-aarch64-full is red for a month. https://lab.llvm.org/buildbot/#/builders/7?numbuilds=700 Could you move linaro-aarch64-full to the staging and make it green again, please? Please let me know if I could help or you have questions. Thanks Galina

5 years, 1 month

Re: Clang targetting x64 linker

by Maxim Kuvyrkov

Hi Joel, Indeed, LLD is not configured to be used by default in LLVM-12.0.0-rc1. You need to add -fuse-ld=lld option for it to work. We’ll fix this in the final LLVM-12 release for WoA, which is expected in around 2 weeks. Thanks for catching this! c:\Users\tcwg\source\maxim>..\llvm-12.0.0-rc1\bin\clang-cl.exe hello.c clang-cl: error: unable to execute command: Couldn't execute program 'C:\BuildTools\VC\Tools\MSVC\14.28.29333\bin\Hostx64\arm64\link.exe': Unknown error (0xD8) clang-cl: error: linker command failed with exit code 1 (use -v to see invocation) c:\Users\tcwg\source\maxim>..\llvm-12.0.0-rc1\bin\clang-cl.exe -fuse-ld=lld hello.c c:\Users\tcwg\source\maxim>hello.exe Hello c:\Users\tcwg\source\maxim>..\llvm-12.0.0-rc1\bin\clang.exe -fuse-ld=lld hello.c c:\Users\tcwg\source\maxim>hello.exe Hello -- Maxim Kuvyrkov https://www.linaro.org > On 4 Mar 2021, at 19:43, Joel Cox <Joel.Cox(a)arm.com> wrote: > > Hi > > I was trying "clang hello.c" from command line, but "clang-cl hello.c" gives me the same error. I am unsure if this is what you mean but neither work. > > Thanks, > Joel > > -----Original Message----- > From: Maxim Kuvyrkov <maxim.kuvyrkov(a)linaro.org> > Sent: 04 March 2021 16:40 > To: Joel Cox <Joel.Cox(a)arm.com> > Cc: linaro-toolchain(a)lists.linaro.org > Subject: Re: Clang targetting x64 linker > > Hi Joel, > > Are you using clang-cl.exe as compiler/linker driver? It’s easiest to use clang-cl.exe as it aims to be a direct replacement for MSVC’s cl.exe, but will use LLVM tools. In particular, when clang-cl.exe uses LLVM Linker (LLD) by default. > > If you are using linux-style clang.exe as the driver, then you need to specify -fuse-ld=lld to use LLD. > > Does this help? > > Regards, > > -- > Maxim Kuvyrkov > https://www.linaro.org > >> On 4 Mar 2021, at 19:11, Joel Cox <Joel.Cox(a)arm.com> wrote: >> >> Hi >> >> I've been trying to run clang on a Windows on Arm machine, but it keeps trying to using the link.exe located in "Visual studio/..../Host64/arm64", which is (seemingly) an x64 tool and as such doesn't run, and crashes the process. >> Is there a way to set clang to look at VS's x86 link.exe? Or if there is an arm64 version that clang should be using instead? >> >> Thanks, >> Joel >> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. >> _______________________________________________ >> linaro-toolchain mailing list >> linaro-toolchain(a)lists.linaro.org >> https://lists.linaro.org/mailman/listinfo/linaro-toolchain > > IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

5 years, 1 month

[ACTIVITY] week ending 14 Mar 2021

by Richard Henderson

[UM-2] * Clean up tcg code_gen_buffer mapping. * Clean up ppc tb->flags madness. * Rebase tci clean up. * Random patch review. [VIRT-349] * Send v4 of sve2 patch set. r~

5 years, 1 month

[ACTIVITY] week ending Mar. 14 2021

by Alex Bennée

VirtIO Initiative ([STR-9]) =========================== - attended the [rust-vmm sync call] [rust-vmm sync call] <https://etherpad.opendev.org/p/rust-vmm-sync-2021> VirtIO RPMB ([STR-5]) - followed more of [RFC PATCH 0/5] RPMB internal and user-space API + WIP virtio-rpmb frontend Message-Id: <CACRpkda9f-BNmu-CaNsghnDoOcSXvvvji=tag2Xos+tg_nNZ0w(a)mail.gmail.com> [STR-5] <https://projects.linaro.org/browse/STR-5> [Rust version of virtio-rpmb] <https://github.com/stsquad/virtio-rpmb> QEMU Upstream Work ([UM-2]) =========================== - posted [qemu-web PATCH] pages: update deprecation policy links to "official" manual Message-Id: <20210308103049.3653-1-alex.bennee(a)linaro.org> - posted [qemu-web RFC PATCH] _download/source.html: show the GPG fingerprint for releases Message-Id: <20210308111649.14898-1-alex.bennee(a)linaro.org> - posted [PATCH v2 0/4] semihosting/next (SYS_HEAPINFO fix) Message-Id: <20210309141727.12522-1-alex.bennee(a)linaro.org> - posted [PULL 00/18] testing, docs, semihosting move and guest-loader Message-Id: <20210308135104.24903-1-alex.bennee(a)linaro.org> - posted [PULL v2 00/15] testing, docs, semihosting move and guest-loader Message-Id: <20210310160002.11659-1-alex.bennee(a)linaro.org> - posted [PATCH v1 0/7] testing/next (hexagon 2, electric boogaloo) Message-Id: <20210310192331.29284-1-alex.bennee(a)linaro.org> - posted [PULL v2 00/15] testing, docs, semihosting move and guest-loader Message-Id: <20210310160002.11659-1-alex.bennee(a)linaro.org> - posted [PATCH v3 0/4] semihosting/next (SYS_HEAPINFO) Message-Id: <20210309172127.20470-1-alex.bennee(a)linaro.org> - posted [PATCH v5 0/5] semihosting/next (SYS_HEAPINFO) Message-Id: <20210312102029.17017-1-alex.bennee(a)linaro.org> - posted [PATCH v1 00/14] plugins/next (phys addr, syscalls, lots of docs) Message-Id: <20210312172821.31647-1-alex.bennee(a)linaro.org> [UM-2] <https://projects.linaro.org/browse/UM-2> Completed Reviews [3/3] ======================= [PATCH v2] linux-user: Fix executable page of /proc/self/maps Message-Id: <20210308091959.986540-1-nsurbayrole(a)quarkslab.com> [PATCH] plugins: new syscalls plugin Message-Id: <20200812115816.4454-1-matthias(a)weckbecker.name> Added: <2020-08-12 Wed> [PATCH v2] plugins: Expose physical addresses instead of device offsets Message-Id: <20210309202802.211756-1-aaron(a)os.amperecomputing.com> Absences ======== - Lockdown 3: Half day schooling - ends soon! Current Review Queue ==================== TODO [PATCH 0/4] Upgrade Meson to 0.57.x Message-Id: <20210310104937.253532-1-pbonzini(a)redhat.com> ================================================================================================= TODO [RFC v3 00/23] arm cleanup experiment for kvm-only build Message-Id: <20210303114053.20305-1-cfontana(a)suse.de> ================================================================================================================== Added: <2021-03-04 Thu> TODO [RFC PATCH 0/5] target/arm: Add MTE support to KVM guest Message-Id: <cover.1612747873.git.haibo.xu(a)linaro.org> =================================================================================================================== Added: <2021-02-16 Tue> TODO [PATCH v2 00/15] tcg/arm: host neon support -- Alex Bennée

5 years, 1 month

[ACTIVITY] 8-12 March 2021

by Christophe Lyon

== Progress == * GCC upstream validation: - Bisected last week regressions, but there had already been reported/fixed. * GCC - MVE autovectorization: - vcmp support mostly complete. support of FP types looks OK, though trickier than expected. - vld2/vst2 and vld4/vst4 done. * Misc - stm32 benchmarking harness: good speed up after removing useless toolchain multilib builds (7 minutes vs 1h+) - fixed GCC bisect Jenkins job == Next == * MVE auto-vectorization/intrinsics improvements * GCC/cortex-M testing improvements & fixes * cortex-m benchmarking * Resume GDB/FDPIC work * Troubleshoot Jenkins problems

5 years, 1 month

[ACTIVITY] report week ending 12 Mar

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - Mostly caught up on code review now: have done all the patches that are targeting 6.0 - Sent out some pullreqs with for-6.0 material - Wrote a patch to make us emulate the right number of counters for the PMU according to what each CPU should have, rather than always 4 - Had a go at fixing the M-profile vector table load on reset to handle aliased memory regions * QEMU-364 [QEMU support for ARMv8.1-M extensions] - mps3-an524 and -an547 patchseries now in master: this epic is done! thanks -- PMM

5 years, 1 month

Pre-commit CI with libc++

by Louis Dionne

Folks, I am pleased to announce the move of libc++ to pre-commit CI. Over the past few months, we have set up Buildkite jobs on top of the Phabricator integration built by Mikhail and Christian, and we now run almost all of the libc++ build bots whenever a Phabricator review is created. The bots also run when a commit is pushed to the master branch, similarly to the existing Buildbot setup. You can see the libc++ pipeline in action here: https://buildkite.com/llvm-project/libcxx-ci. This is great -- we’ve been waiting to set up pre-commit CI for a long time, and we’ve seen a giant productivity gain since it’s up. I think everyone who contributes to libc++ greatly benefits, seeing how reviews are now used to trigger CI and improve our confidence in changes. This change does have an impact on existing build bots that are not owned by one of the libc++ maintainers. While I transferred the build bots that we owned (which Eric had set up) to Buildkite, the remaining build bots will have to be moved to Buildkite by their respective owners. These builds bots are (owners in CC): libcxx-libcxxabi-x86_64-linux-debian libcxx-libcxxabi-x86_64-linux-debian-noexceptions libcxx-libcxxabi-libunwind-x86_64-linux-debian libcxx-libcxxabi-singlethreaded-x86_64-linux-debian libcxx-libcxxabi-libunwind-armv7-linux libcxx-libcxxabi-libunwind-armv8-linux libcxx-libcxxabi-libunwind-armv7-linux-noexceptions libcxx-libcxxabi-libunwind-armv8-linux-noexceptions libcxx-libcxxabi-libunwind-aarch64-linux libcxx-libcxxabi-libunwind-aarch64-linux-noexceptions The process of moving these bots over to Buildkite is really easy. Please take a look at the documentation at https://libcxx.llvm.org/docs/AddingNewCIJobs.html#addingnewcijobs and contact me if you need additional help. To make sure we get the full benefits of pre-commit CI soon, I would like to put a cutoff date on supporting the old libc++ builders at http://lab.llvm.org:8011/builders. I would propose that after January 1st 2021 (approx. 1 month from now), the libc++ specific build bots at lab.llvm.org be removed in favor of the Buildkite ones. If you currently own a bot, please make sure to add an equivalent Buildkite bot by that cutoff date to make sure your configuration is still supported, or let me know if you need an extension. Furthermore, with the ease of creating new CI jobs with this infrastructure, we will consider any libc++ configuration not covered by a pre-commit bot as not explicitly supported. It doesn’t mean that such configurations won’t work -- it just means that we won’t be making bold claims about supporting configurations we’re unable to actually test. So if you care about a configuration, please open a discussion and let’s see how we can make sure it's tested properly! I am thrilled to be moving into the pre-commit CI era. The benefits we see so far are huge, and we're loving it. Thanks, Louis PS: This has nothing to do with a potential move or non-move to GitHub. The current pre-commit CI works with Phabricator, and would work with GitHub if we decided to switch. Let’s try to keep those discussions separate :-). PPS: We’re still aiming to support non libc++ specific Buildbots. For example, if something in libc++ breaks a Clang bot, we’ll still be monitoring that. I’m just trying to move the libc++-specific configurations to pre-commit.

5 years, 1 month

[ACTIVITY] week ending 7 Mar 2021

by Richard Henderson

[VIRT-349 # QEMU SVE2 Support ] I have a working FVP SVE2 install! I used a new FVP version (11.13.36) from the last time that I tried (11.13.21 on Jan 27). I used a debian-testing snapshot from 1-MAR, which has linux 5.10 bundled, and fvp revc dtb installed. I used https://git.linaro.org/landing-teams/working/arm/arm-reference-platforms.gi… (which is linked to by one of the howtos that Peter forwarded) and chose the "pre-built uefi" version. I need to report a bug on this build script -- the "build from source" option does not work on a system that has all python3 and no python2. I've rebuilt all of the risu trace files for vq=4 (512-bit). I'm now refreshing my qemu branch to test. [UM-61 # TCG Core Maintainership ] PR for patch queue; aa64 fixes, tci fixes, tb_lookup cleanups. [UM-2 # Upstream Maintainership ] Patch review, mostly v8.1m board stuff. r~

5 years, 1 month

[ACTIVITY] week ending Mar. 7 2021

by Alex Bennée

VirtIO Initiative ([STR-9]) =========================== - posted [PATCH v2] vhost-user.rst: add clarifying language about protocol negotiation Message-Id: <20210303145011.14547-1-alex.bennee(a)linaro.org> Linux Userspace ABI for RPMB devices ([STR-31]) ----------------------------------------------- - posted [RFC PATCH 0/5] RPMB internal and user-space API + WIP virtio-rpmb frontend Message-Id: <20210303135500.24673-1-alex.bennee(a)linaro.org> - has stimulated discussion on the thread, will see next posting from Thomas QEMU Upstream Work ([UM-2]) =========================== - posted [PATCH v1 0/9] testing/next (docs, hexagon, cfi, docker) Message-Id: <20210305092328.31792-1-alex.bennee(a)linaro.org> - posted [PATCH v1 0/3] semihosting/next (move from hw, heapinfo) Message-Id: <20210305135451.15427-1-alex.bennee(a)linaro.org> - optimising tb lookup ---------------------- - CLOSING NOTE [2021-03-05 Fri 17:22] rth merged my changes plus a pre-compute of cflags. Completed Reviews [8/8] ======================= [PATCH v3 0/2] gitlab-ci.yml: Add jobs to test CFI Message-Id: <20210304030948.9367-1-dbuono(a)linux.vnet.ibm.com> [PATCH 0/4] hexagon: Add Docker image & testing to gitlab-ci Message-Id: <20210228222314.304787-1-f4bug(a)amsat.org> - CLOSING NOTE [2021-03-04 Thu 20:04] Queued to my tree Added: <2021-03-02 Tue> [PATCH v2] tests/docker: Use --arch-only when building Debian cross image Message-Id: <20210223211115.2971565-1-f4bug(a)amsat.org> [PATCH] linux-user: Adjust pgd_find_hole_fallback result with guest_loaddr Message-Id: <20210303094919.x6wnlh6qulx72fz6(a)titan.localdomain> - CLOSING NOTE [2021-03-05 Fri 14:12] Added: <2021-03-03 Wed> [PATCH 00/44] hw/arm: New board model mps3-an547 Message-Id: <20210219144617.4782-1-peter.maydell(a)linaro.org> - CLOSING NOTE [2021-03-05 Fri 14:14] Looks like others have already looked over it. ADDED: <2021-03-04 Thu> [PATCH v3 00/70] TCI fixes and cleanups Message-Id: <20210208023752.270606-1-richard.henderson(a)linaro.org> - CLOSING NOTE [2021-03-05 Fri 16:59] v4 released, wish I'd noticed earlier ;-) Added: <2021-02-08 Mon> [PATCH 00/27] tcg patch queue Message-Id: <20210302175741.1079851-1-richard.henderson(a)linaro.org> [PATCH 0/3] docs: replace master/slave with more accurate wording Message-Id: <20210226143413.188046-1-pbonzini(a)redhat.com> Absences ======== - Lockdown 3: Half day schooling - ends soon! Current Review Queue ==================== TODO [RFC v3 00/23] arm cleanup experiment for kvm-only build Message-Id: <20210303114053.20305-1-cfontana(a)suse.de> ================================================================================================================== Added: <2021-03-04 Thu> TODO [RFC PATCH 0/5] target/arm: Add MTE support to KVM guest Message-Id: <cover.1612747873.git.haibo.xu(a)linaro.org> =================================================================================================================== Added: <2021-02-16 Tue> TODO [PATCH v2 00/15] tcg/arm: host neon support Message-Id: <20210208024625.271018-1-richard.henderson(a)linaro.org> ================================================================================================================== Added: <2021-02-08 Mon> -- Alex Bennée

5 years, 1 month

[ACTIVITY] report week ending 5 Mar

by Peter Maydell

Progress (short week, 2 days): * Some time spent on setting up new work laptop * Started in on the pile of code review that had built up while I was on holiday... made a bit of progress and sent out one pullreq. Queue length now: 16 series. thanks -- PMM

5 years, 1 month

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain