All,
During Connect the suggestion was made that each working group should have
its own IRC Channel for discussions and topics relating to the group in
particular (as opposed to #linaro which is 'generic' Linaro conversations).
Therefore I have just set up #linaro-tcwg on Freenode for the Toolchain
Working Group.
This channel is public and open to anyone who wants to talk with the TCWG
group about anything toolchain related.
Thanks,
Matt
--
Matthew Gretton-Dann
Toolchain Working Group, Linaro
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.
VirtIO Initiative ([STR-9])
===========================
- Raised [STR-21] to cover some Zephyr work
- Synced with EPAM and ARM to discuss their work and direction
[STR-21] <https://projects.linaro.org/browse/STR-21>
VirtIO RPMB ([STR-5])
=====================
- Started investigating Rust port of vhost-user-rpmb
[STR-5] <https://projects.linaro.org/browse/STR-5>
VirtIO Portability Demo ([STR-13])
==================================
- delivered gold copy for talk at [OSS and ALS Japan 2020]
- synced with ALS guys on talk
[OSS and ALS Japan 2020] <https://sched.co/f2Yk>
QEMU Upstream Work ([UM-2])
===========================
- posted [PATCH v1 for 5.1 00/10] various fixes (CI, Xen, plugins)
Message-Id: <20201110192316.26397-1-alex.bennee(a)linaro.org>
- posted [[PULL for 5.2-rc3 0/7] various CI cleanups (scripts,
avocado, gitlab)]
[UM-2] <https://projects.linaro.org/browse/UM-2>
[[PULL for 5.2-rc3 0/7] various CI cleanups (scripts, avocado, gitlab)]
<mu4e:i:20201123112518.13425-1-alex.bennee@linaro.org>
Completed Reviews [4/4]
=======================
[for-5.2 0/9] docs: Move orphan top-level .rst files into manuals
Message-Id: <20201112144041.32278-1-peter.maydell(a)linaro.org>
[PATCH v3 00/41] Mirror map JIT memory for TCG
Message-Id: <20201106032921.600200-1-richard.henderson(a)linaro.org>
- CLOSING NOTE [2020-11-14 Sat 11:52]
Had a brief look over, waiting for next revision
Added: <2020-11-06 Fri>
[PATCH v2 00/13] Remove GCC < 4.8 checks
Message-Id: <20201126112915.525285-1-marcandre.lureau(a)redhat.com>
[PATCH] gdbstub: Correct misparsing of vCont C/S requests
Message-Id: <20201121210342.10089-1-peter.maydell(a)linaro.org>
Absences
========
- Illness
Current Review Queue
====================
* [PATCH v2 0/4] linux/sparc: more get/set_context fixes
Message-Id: <20201106152738.26026-1-peter.maydell(a)linaro.org>
Added: <2020-11-06 Fri>
* [PATCH 0/8] arm/virt: add usb support
Message-Id: <20201023071022.24916-1-kraxel(a)redhat.com>
Added: <2020-10-27 Tue>
* [PATCH 0/4] riscv: Add semihosting support [v10]
Message-Id: <20201026212853.92880-1-keithp(a)keithp.com>
Added: <2020-10-27 Tue>
* [PATCH v2 0/7] xen/arm: Unbreak ACPI
Message-Id: <20201023154156.6593-1-julien(a)xen.org>
Added: <2020-10-24 Sat>
--
Alex Bennée
Progress:
* UM-2 [QEMU upstream maintainership]
+ Cut rc3; there were a few last-minute bugfixes that came in
so we will need an rc4
* VIRT-364 [QEMU support for ARMv8.1-M extensions]
+ read through the SSE-300 TRM and identified the required work
to model it (it's similar to the SSE-200 which we already have
but with various minor changes and a couple of new devices)
* wisdom tooth extracted \o/
thanks
-- PMM
[UM-59 # FPU Emulation Maintainership ]
Lots more work converting to FloatParts.
Almost all floatx80 now converted.
Still to do are log2 and rem/mod for full conversion.
r~
Generally productive week rather derailed at the end by
a sudden onset of toothache Thursday night :-/
Progress:
* UM-2 [QEMU upstream maintainership]
+ usual release cycle work
* VIRT-364 [QEMU support for ARMv8.1-M extensions]
+ Worked through the remaining set of identified new features
for v8.1M implementing them.
+ Fixed a handful of pre-existing bugs along the way.
+ Sent out a patchset with all this plus the "Implement (no-MVE) Cortex-M55
model" patch on top, since we now have all the pieces needed for it.
+ The next and final piece of work here is to implement a model
of a board that uses the Cortex-M55.
-- PMM
