There’s been an ongoing failure on the clang-cmake-armv8-selfhost
builder for the last day or so; see e.g.:
http://lab.llvm.org:8011/builders/clang-cmake-armv7-selfhost/builds/2827/
This list is recorded as the contact information for that builder.
It is apparently crashing in a tblgen backend that I just added:
```
Stack dump:
0. Program arguments:
/home/buildslave/buildslave/clang-cmake-armv7-selfhost/stage1/bin/clang-tblgen
-gen-clang-type-writer -I
/home/buildslave/buildslave/clang-cmake-armv7-selfhost/llvm/clang/include
-I
/home/buildslave/buildslave/clang-cmake-armv7-selfhost/llvm/clang/include/clang/AST
-I
/home/buildslave/buildslave/clang-cmake-armv7-selfhost/llvm/llvm/include
/home/buildslave/buildslave/clang-cmake-armv7-selfhost/llvm/clang/include/clang/AST/TypeProperties.td
--write-if-changed -o
/home/buildslave/buildslave/clang-cmake-armv7-selfhost/stage1/tools/clang/include/clang/AST/AbstractTypeWriter.inc
Segmentation fault (core dumped)
```
I would like to fix this, but I have no ability to reproduce it, and the
crash information in the log is quite minimal. Is there a way I can get
a shell on a system that can reproduce this, or at the very least get a
line number for where exactly it is crashing?
John.
The Arm GNU Toolchain for the A-profile Architecture
=====================================================
We are pleased to announce the Arm release of the pre-built GNU cross-toolchain
for the A-profile cores: GCC 9.2-2019.12.
Further information about the GNU Arm toolchain and the release packages is
available at Arm Developer site
https://developer.arm.com/open-source/gnu-toolchain/gnu-a/downloads
Features
========
* Based on GCC 9.2 (See https://gcc.gnu.org/gcc-9/changes.html for details).
Supported targets
=================
* On Windows(x86_64):
- AArch64 (bare-metal and Linux)
- AArch32 (bare-metal and Linux hard-float)
* On Linux(x86_64):
- AArch64 (bare-metal, Linux and Linux big-endian)
- AArch32 (bare-metal and Linux hard-float)
* On Linux(AArch64)
- AArch64 (bare-metal)
- AArch32 (bare-metal and Linux hard-float)
Changes since Arm release GCC 8.3-2019.03
=========================================
* Additional AArch64 hosted cross-toolchains for AArch64 (bare-metal) and
AArch32 (bare-metal and Linux hard-float)
* Additional Windows hosted cross-toolchains for AArch64 (Linux) and
AArch32 (Linux hard-float)
* Retired Linux(x86_64) toolchain for AArch64 (big-endian bare-metal) and
AArch32 (Linux soft-float)
* Changed toolchain naming convention to match standard target triplet
naming convention, with vendor name being none.
For example, arm-eabi is now arm-none-eabi.
* Fixed the Windows toolchain convention to correctly include mingw-w64
instead of mingw32
Host Requirements
==================
* x86-64 Linux: Ubuntu 16.04 LTS or later, or RHEL 7 or later
* AArch64 Linux: Ubuntu 18.04 LTS or later, or RHEL 8
* x86 Windows: Windows 10
Package Versions
=================
* GCC 9.2.1
* glibc 2.30
* binutils 2.33.1
* GDB 8.3.0
* libexpat 2.2.5
* Linux Kernel v4.20.13
* libgmp 4.3.2
* libisl 0.15
* libmpfr 3.1.6
* libmpc 1.0.3
* libiconv 1.15
Contact Arm
===========
For any questions, please use the Arm Communities forums at:
https://community.arm.com/tools/
Please report any bugs via the Linaro Bugzilla at:
https://bugs.linaro.org/
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.
* One day off
o LLVM:
* Couple of failures with the bots
* Machine Outliner:
- Completed testcases
- Validation before re-submission
o Misc
* Various meetings and discussions.
[VIRT-327 # Richard's upstream QEMU work ]
Following up on the feedback from last week on VHE and PAN, posted a patch set
eliminating MMU_MODE*_SUFFIX, and the current limit of NB_MMU_IDX <= 12 that
went with that.
Some patch review.
r~
== Progress ==
* GCC:
- -mpure-code on v6m: waiting for approval, pinged again.
* BFD Linker:
- GNU-629: non-contiguous memory support: Looking at how to handle the
case where input sections change size during the linker iterations.
* GCC upstream validation:
- reported/checked a few issues
* misc:
- infra fixes / troubleshooting / reviews
== Next ==
* GCC: pure-code/v6m, handle feedback
* Binutils: GNU-629: support non-contiguous memory regions in linker
== Future ==
Holidays: Dec 23rd-Jan 2nd
Morello:
- Updated clang driver to use lld with --image-base rather than a linker script.
- LLD changes merged.
- Fixed up a few problems spotted by CI and a test on the examples.
- Thoughts on code sequences for an experimental descriptor based ABI.
LLD:
- Committed changes to fix branch patch and thunks interaction in
instrumented Chromium build
- Discussion about deploying BTI in large programs like Chromium with
pre-compiled objects and lots of assembler files.
Planned absences
On holiday for the rest of the decade. First day back in the office 6th January
QEMU Tooling ([VIRT-252])
=========================
Extend gdbstub for SVE ([VIRT-281])
- worked on [v3 rebase]
- added a new test case and discovered a bug in upstream gdbserver
- raised [GNU-647] to track it
[v3 rebase] https://github.com/stsquad/qemu/tree/sve-registers-v3
[GNU-647] https://projects.linaro.org/browse/GNU-647
QEMU ARMv8.1 VHE ([VIRT_263])
=============================
- bunch of review and testing of rth's v4 series
[VIRT_263] https://projects.linaro.org/browse/VIRT-263
Upstream Work ([VIRT-109])
==========================
- posted {PATCH v2 0/6} linux-user mmap debug cleanup Message-Id:
<20191206110354.GA775461(a)stefanha-x1.localdomain>
Completed Reviews [8/8]
=======================
{PATCH 0/3} iotests: Check for the possibility to create large files
Message-Id: <20191202101631.10003-1-thuth(a)redhat.com>
- CLOSING NOTE [2019-12-03 Tue 10:14]
Preparatory for the multiarch Travis tests.
Added: <2019-12-02 Mon>
{PATCH v2 0/2} Run tcg tests with tci on Travis
Message-Id: <20191128153525.2646-1-thuth(a)redhat.com>
- CLOSING NOTE [2019-12-03 Tue 10:21]
will take v3 with --disable-kvm and sparc tweaks
Added: <2019-11-28 Thu>
{PATCH 0/2} flush CPU TB cache in breakpoint_invalidate
Message-Id: <20191127220602.10827-1-jcmvbkbc(a)gmail.com>
- CLOSING NOTE [2019-12-03 Tue 11:20]
Needs a slightly neater solution than always flushing everything.
Added: <2019-11-28 Thu>
{PATCH 0/1} tests/vm: Allow to set path to qemu-img
Message-Id: <20191114134246.12073-1-wainersm(a)redhat.com>
- CLOSING NOTE [2019-12-03 Tue 11:37]
Queued to my tree
Added: <2019-11-14 Thu>
{PATCH 0/4} docker: Update Travis-CI image to run acceptance tests
Message-Id: <20190818231827.27573-1-philmd(a)redhat.com>
- CLOSING NOTE [2019-12-03 Tue 16:03]
Will wait for next iteration.
{PATCH 0/4} python/qemu: New accel module and improvements
Message-Id: <20191115180829.10275-1-wainersm(a)redhat.com>
- CLOSING NOTE [2019-12-03 Tue 17:00]
All looks good. I assume will be merged with another series that
uses the new features.
Added: <2019-11-28 Thu>
{PATCH v7 0/8} Acceptance test: Add "boot_linux" acceptance test
Message-Id: <20191104151323.9883-1-crosa(a)redhat.com>
- CLOSING NOTE [2019-12-03 Tue 19:20]
Broken for me with load_module failure
Added: <2019-11-04 Mon>
{PATCH v4 00/40} target/arm: Implement ARMv8.1-VHE
Message-Id: <20191203022937.1474-1-richard.henderson(a)linaro.org>
- CLOSING NOTE [2019-12-06 Fri 18:35]
Reviewed about half the patch set, will do the remainder on v5 once
Peter's comments are addressed.
Added: <2019-12-03 Tue>
Current Review Queue
====================
* {PATCH} Semihost SYS_READC implementation (v6)
Message-Id: <20191104204230.12249-1-keithp(a)keithp.com>
Added: <2019-12-06 Fri>
* {PATCH 0/2} tests/acceptance: Add boot vmlinux test
Message-Id: <20191206140012.15517-1-wainersm(a)redhat.com>
Added: <2019-12-06 Fri>
* {RFC PATCH 00/10} hw/avr: Introduce the Arduino board
Message-Id: <20191128015030.27543-1-f4bug(a)amsat.org>
Added: <2019-11-28 Thu>
* {RFC 0/3} tests/vhost-user-fs-test: add vhost-user-fs test case
Message-Id: <20191025100152.6638-1-stefanha(a)redhat.com>
Added: <2019-10-25 Fri>
--
Alex Bennée
Morello:
- Static linking patches committed to merge branch.
- Dynamic linking patches up for review.
- Agreed definition of what LLD for stage-1 looks like.
- Discussions on what linker and ABI work is likely to be needed for stage-2.
Linaro:
Some LLD thunk/patch generation problems
https://bugs.llvm.org/show_bug.cgi?id=44071 for a gigantic build of
Chromium > 260 Mb .text section on AArch64. Diagnosed problems but
will need to fix next week.
Some support for ClangBuiltLinux with respect to some integrated
assembler compatibility with GNU as.
Buildbot duty.
Pretty quiet, attempted to reproduce some timeouts seen on the LNT
generate cmake. 3 minutes on an lightly loaded machine, exceeding 20
minutes in some cases on the heavily loaded buildbot host. Seems to
have resolved itself with the latest container update.
- Some changes to BTI for the Android team. All committed upstream.
-- Adding PT_GNU_PROPERTY support.
-- Increasing alignment of .note.gnu.property section to 8.
Holiday
- On holiday from Monday 16th to 3rd January inclusive. Back in office
January 6th.
Progress:
* VIRT-65 [QEMU upstream maintainership]
- code review (have had a go at cutting down the backlog; down to
six patchsets in my queue...):
+ reviewed the 'clock framework API' patchset; this is
looking good, the only major question to sort out is what
the right internal representation for the clock frq/period is
+ Paolo's series to add kernel-doc support to our Sphinx
setup (which is a mashup of something I hacked together
ages ago and more recent work from him)
+ RAS memory error support for KVM guests (mostly
reviewing the easy bits and noting that others have
provided code review comments on the rest)
+ reviewed RTH's MemTag emulation series
+ reviewed the bits of RTH's VHE series that Alex hadn't got to
+ tested an arm/acpi patchset from Huawei from March
which had unfortunately fallen through the cracks.
It failed 'make check' so they'll need to fix and resubmit :-(
- release work:
+ we needed an rc4
+ and it looks like we'll need an rc5 for one last important
bugfix; I'm hoping we can do an rc and then actual release
a few days later, though
thanks
-- PMM
