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.
Please see
https://lists.ubuntu.com/archives/ubuntu-devel/2021-January/041341.htmlhttps://wiki.ubuntu.com/ToolChain/LTO
Some builds only fail on AArch64, these are:
buildlog_ubuntu-hirsute-arm64.abiword_3.0.4~dfsg-2_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.adabrowse_4.0.3-12_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.adacontrol_1.21r6b-5_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.armnn_19.11.1-1_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.cctools_7.1.2-2ubuntu3_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.csound_1:6.14.0~dfsg-6build1_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.dh-ada-library_6.20_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.dietlibc_0.34~cvs20160606-12_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.entropybroker_2.9-3build2_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.fpc_3.2.0+dfsg-8build2_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.grcompiler_5.2-2.1_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.haskell-hopenpgp-tools_0.23.1-1build2_BUILDING.txt.gz
arm64
buildlog_ubuntu-hirsute-arm64.ignition-common_3.5.0+dfsg1-4_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.lazarus_2.0.10+dfsg-4_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.lepton-eda_1.9.13-1_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.libcxx-serial_1.2.1-4_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.minetest_5.3.0+repack-1_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.ogre-1.12_1.12.5+dfsg1-1ubuntu1_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.openmsx_16.0-1_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.parsinsert_1.04-7ubuntu1_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.prometheus-alertmanager_0.21.0+ds-2build1_BUILDING.txt.gz
arm64
buildlog_ubuntu-hirsute-arm64.pyqt5_5.15.2+dfsg-1_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.racon_1.4.13-2build1_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.rampler_1.1.1-3_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.ruby-http-parser.rb_0.6.0-5_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.shasta_0.6.0-4build1_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.snd_20.9-1_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.sogo_4.3.2-1_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.swiglpk_4.65.0-2build3_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.synfig_1.2.2+dfsg-3build3_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.synfigstudio_1.2.2-1build1_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.tcc_0.9.27+git20200814.62c30a4a-1_BUILDING.txt.gz
arm64
buildlog_ubuntu-hirsute-arm64.unar_1.10.1-2build9_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.valgrind_1:3.16.1-1ubuntu1_BUILDING.txt.gz arm64
buildlog_ubuntu-hirsute-arm64.vulkan-tools_1.2.154.0+dfsg1-1_BUILDING.txt.gz arm64
Note that some of those like the Ada related ones are false positives, and I
didn't look at the arm64 specific issues yet.
All builds were done using the GCC 10 branch.
Matthias
VirtIO Initiative ([STR-9])
===========================
- some prep for next weeks TSC
QEMU Device and Machine Models ([QEMU-418])
===========================================
- added a bunch of new cards for ARMv8.7 features using ARMs new
feature type
QEMU Support for Xen ([STR-20])
===============================
- latest iteration of [PATCH V6 00/24] IOREQ feature (+ virtio-mmio)
on Arm Message-Id:
<1611884932-1851-1-git-send-email-olekstysh(a)gmail.com>
- while re-basing [my Xen loader and fixes tree]
- realised that [PATCH v4 00/12] Support disabling TCG on ARM (part
2) Message-Id: <20200929224355.1224017-1-philmd(a)redhat.com> would
be useful
- which awaits [PATCH v14 00/22] i386 cleanup PART 2 Message-Id:
<20210128092814.8676-1-cfontana(a)suse.de> being merged
[STR-20] <https://projects.linaro.org/browse/STR-20>
[my Xen loader and fixes tree]
<https://github.com/stsquad/qemu/tree/xen/guest-loader-and-arm-build-cleanup…>
QEMU Upstream Work ([UM-2])
===========================
- posted [PATCH v1 0/2] meson fixups for check-tcg/softfloat
Message-Id: <20210126145356.7860-1-alex.bennee(a)linaro.org>
- posted some documentation patches while helping LKFT team get up and
running
- [PATCH] docs/system: document an example vexpress-a15 invocation
Message-Id: <20210128185300.2875-1-alex.bennee(a)linaro.org>
[UM-2] <https://projects.linaro.org/browse/UM-2>
Completed Reviews [3/3]
=======================
[PATCH v4 0/4] meson: Try to clarify TCG / TCI options for new users
Message-Id: <8f1f2dc6-5ad2-7d48-c2f9-9afa1e4d4065(a)weilnetz.de>
[PATCH 00/23] TCI fixes and cleanups
Message-Id: <20210128082331.196801-1-richard.henderson(a)linaro.org>
[PATCH] accel/tcg: Add URL of clang bug to comment about our workaround
Message-Id: <20210129130330.30820-1-peter.maydell(a)linaro.org>
Absences
========
- Lockdown 3: Home schooling returns!
Current Review Queue
====================
* [PATCH V6 00/24] IOREQ feature (+ virtio-mmio) on Arm
Message-Id: <1611884932-1851-1-git-send-email-olekstysh(a)gmail.com>
Added: <2021-01-29 Fri>
* [RFC PATCH 0/4] hw/intc: enable GICv4 memory layout for GICv3 driver
Message-Id: <20210124025306.3949-1-leif(a)nuviainc.com>
Added: <2021-01-25 Mon>
* [PATCH v3 00/21] target-arm: Implement ARMv8.5-MemTag, user mode
Message-Id: <20210115224645.1196742-1-richard.henderson(a)linaro.org>
Added: <2021-01-18 Mon>
* [PATCHv3 00/17] ARMv8.4 Secure EL2
Message-Id: <3333301.iIbC2pHGDl(a)basile.remlab.net>
Added: <2020-12-08 Tue>
--
Alex Bennée
Progress:
* UM-2 [QEMU upstream maintainership]
+ usual upstream maintenance, code review, etc
* QEMU-364 [QEMU support for ARMv8.1-M extensions]
+ CMSDK Clock changes now upstream
+ When integrating those with the SSE timer model, found what seem like
some more clock API changes we could use; patches in progress
Some Arm-internal training and similar admin tasks this week.
thanks
-- PMM
[UM-61 TCG Maint]
3 different attempts at fixing the out-of-temps
failure produced by the tcg-constant patch set.
The last, longjmp to restart w/ a smaller tb,
seems unlikely to have unanticipated side effects.
[UM-2 QEMU Maint]
Refresh two patches toward cortex-a76.
Misc patch review.
Partial fix for target/ppc mis-use of tb->flags.
r~
VirtIO Initiative ([STR-9])
===========================
- posted Project Stratos planning priorities for the next development
cycle (-> Oct2021) Message-Id: <87im7rtpyq.fsf(a)linaro.org>
- baring feedback from members during voting I think this is what we
are doing
- attended [AGL discussion] on zero-copy for virtio-gpu with Peter
Griffin
- more meetings on other collaboration opportunities, drew more slide
ware
- bootstrapped my RB5 rig, just need to figure out how to update the
kernel
[STR-9] <https://projects.linaro.org/browse/STR-9>
[AGL discussion]
<https://confluence.automotivelinux.org/display/VE/Meeting+Agenda?src=contex…>
QEMU Device and Machine Models ([QEMU-418])
===========================================
- flurry of syncing and card creation, solidified [QEMU-414]
[QEMU-418] <https://projects.linaro.org/browse/QEMU-418>
[QEMU-414] <https://projects.linaro.org/browse/QEMU-414>
QEMU Support for Xen ([STR-20])
===============================
- continued looking at [PATCH V4 00/24] IOREQ feature (+ virtio-mmio)
on Arm Message-Id:
<1610488352-18494-1-git-send-email-olekstysh(a)gmail.com>
[STR-20] <https://projects.linaro.org/browse/STR-20>
QEMU Upstream Work ([UM-2])
===========================
- respun [PULL v2 00/30] testing, gdbstub and semihosting Message-Id:
<20210118111745.20104-1-alex.bennee(a)linaro.org> to fix NetBSD issue
- posted [PATCH v1 0/6] testing/next (docker binfmt tests) Message-Id:
<20210119175208.763-1-alex.bennee(a)linaro.org>
- posted [PATCH v2 0/8] testing/next (docker, binfmt, gdb version)
Message-Id: <20210122181854.23105-1-alex.bennee(a)linaro.org>
[UM-2] <https://projects.linaro.org/browse/UM-2>
Completed Reviews [4/4]
=======================
[PATCH] util/log: flush TB cache when log level changes
Message-Id: <161130982491.1038646.15688151175539344664.stgit@pasha-ThinkPad-X280>
[PATCH v3] hw/core/qdev-properties-system: Rewrite set_pci_host_devaddr using GLib
Message-Id: <20201125083300.861206-1-philmd(a)redhat.com>
[RFC PATCH] tests/docker: Allow passing --network option when building images
Message-Id: <20210119054502.531451-1-f4bug(a)amsat.org>
[PATCH] tcg: Increase the static number of temporaries
Message-Id: <20210121025439.1120405-1-richard.henderson(a)linaro.org>
Absences
========
- Lockdown 3: Home schooling returns!
Current Review Queue
====================
* [PATCH v3 00/21] target-arm: Implement ARMv8.5-MemTag, user mode
Message-Id: <20210115224645.1196742-1-richard.henderson(a)linaro.org>
Added: <2021-01-18 Mon>
* [PATCH 0/6] accel: Restrict TCG-specific code
Message-Id: <20210117164813.4101761-1-f4bug(a)amsat.org>
Added: <2021-01-18 Mon>
* [PATCH V4 00/24] IOREQ feature (+ virtio-mmio) on Arm
Message-Id: <1610488352-18494-1-git-send-email-olekstysh(a)gmail.com>
Added: <2021-01-13 Wed>
* [PATCH v5 00/23] tcg: Better handling of constants
Message-Id: <20201217145215.534637-1-richard.henderson(a)linaro.org>
Added: <2020-12-17 Thu>
--
Alex Bennée
Progress:
* UM-2 [QEMU upstream maintainership]
+ Code review (including RTH's MTE-for-user-mode-emulation)
+ Investigating an intermittent failure of a test case involving
an s390 guest on aarch64 hosts...
* QEMU-364 [QEMU support for ARMv8.1-M extensions]
+ Converted the ARMSSE (IoTKit/SSE-200) code over to use the Clock
framework, which was added to QEMU after ARMSSE was first written.
(This is a prereq for adding the new-in-SSE-300 timer device, which
will use Clocks.) Sent the patches out for review.
I'm currently experimenting with a schedule of:
Mon: JIRA task work; Tue: code review; Thu: JIRA task work; Fri: misc upstream
thanks
-- PMM
