QEMU Device and Machine Models ([QEMU-418])
===========================================
- posted [kvm-unit-tests PATCH v1 0/4] enable LPI and ITS for TCG
Message-Id: <20210428101844.22656-1-alex.bennee(a)linaro.org>
[QEMU-418] <https://projects.linaro.org/browse/QEMU-418>
QEMU Upstream Work ([UM-2])
===========================
- updated [testing/next branch] we some more fixes
[UM-2] <https://projects.linaro.org/browse/UM-2>
[testing/next branch]
<https://github.com/stsquad/qemu/tree/testing/next>
Other
=====
- Spent more time on blog post for [LBO-99]
[LBO-99] <https://projects.linaro.org/browse/LBO-99>
Completed Reviews [3/3]
=======================
[PATCH v3 0/2] tests/docker: tests/tcg/ppc64le: Newer toolchain to build tests for PowerISA v3.1 instructions
Message-Id: <20210423205757.1752480-1-matheus.ferst(a)eldorado.org.br>
[PATCH 0/2] plugins: Freeing allocated values in hash tables.
Message-Id: <20210421140934.7561-1-ma.mandourr(a)gmail.com>
[PATCH v4 00/12] qtests: Check accelerator available at runtime via QMP 'query-accels'
Message-Id: <20210415163304.4120052-1-philmd(a)redhat.com>
[PATCH v2 0/8] GICv3 LPI and ITS feature implementation
Message-Id: <20210401024152.203896-1-shashi.mallela(a)linaro.org>
Absences
========
- Bank Holiday on Monday
Current Review Queue
====================
TODO [PATCH v4 00/12] qtests: Check accelerator available at runtime via QMP 'query-accels'
Message-Id: <20210415163304.4120052-1-philmd(a)redhat.com>
===================================================================================================================================================
TODO [RFC PATCH v2 0/6] hw/arm/virt: Introduce cpu topology support
Message-Id: <20210413080745.33004-1-wangyanan55(a)huawei.com>
==============================================================================================================================
TODO [PATCH v2 00/12] virtio-gpu: Add support for Blob resources feature
Message-Id: <20210420065347.2685768-1-vivek.kasireddy(a)intel.com>
========================================================================================================================================
TODO [RFC v14 00/80] arm cleanup experiment for kvm-only build
Message-Id: <20210416162824.25131-1-cfontana(a)suse.de>
===================================================================================================================
--
Alex Bennée
Progress:
* UM-2 [QEMU upstream maintainership]
- release work: rc5 Monday, and then 6.0 final release on Thursday.
- sent a pullreq with some accumulated arm patches now 6.1 is open
- fixed a trivial bug where WFI in the usermode emulator crashed
* QEMU-406 [QEMU support for MVE (M-profile Vector Extension; Helium)]
- Implemented more instructions: logic ops, VCLS, VCLZ, VREV, VMVN,
VABS, VNEG, VADD, VDUP, VSUB, VMULH, and widening VLDR.
(These are all simple "always call an out-of-line helper" versions.
We'll want an optimised "we know we have no predication" version
for many of them, but I plan to do that afterwards.)
- Worked through the v8M Arm ARM identifying which insns we must
implement. There are 210 insn patterns in total, of which I have
currently implemented 23, so we can produce a rough-and-ready
progress meter: 23/210 (11%)
(There is of course work to do beyond just the insns, but they
form the bulk of it, so the meter has some utility.)
-- PMM
QEMU Support for Xen ([STR-20])
===============================
- continued reviewing [RFC v12 00/65] arm cleanup experiment for
kvm-only build Message-Id: <20210326193701.5981-1-cfontana(a)suse.de>
- this is looking pretty solid now
- cut new version of [arm build clean-ups based on Claudio's series]
- testing reveals some breakage to track down next week
[STR-20] <https://projects.linaro.org/browse/STR-20>
[arm build clean-ups based on Claudio's series]
<https://github.com/stsquad/qemu/tree/xen/arm-build-cleanups-v3>
QEMU Upstream Work ([UM-2])
===========================
- posted [PULL 00/11] rc2 fixes (check-tcg, gitlab, gdbstub)
Message-Id: <20210406150041.28753-1-alex.bennee(a)linaro.org>
- some time trying to debug last weeks PR, eventually merged
- posted [PATCH for post 6.0 v1 00/25] testing/next
(hexagon/tricore/test cc) Message-Id:
<20210419145435.14083-1-alex.bennee(a)linaro.org>
- posted [RFC PATCH] tests/tcg: add a multiarch signals test to stress
test signal delivery Message-Id:
<20210421132931.11127-1-alex.bennee(a)linaro.org>
- hunting for RC failure in s390x
- posted [PATCH] target/s390x: fix s390_probe_access to check
PAGE_WRITE_ORG for writeability Message-Id:
<20210422154427.13038-1-alex.bennee(a)linaro.org>
[UM-2] <https://projects.linaro.org/browse/UM-2>
GSoC/Intern Mentoring
=====================
GSoC 2021 proposal initiation for AGL
Message-Id: <CAC+yH-Z_KZKuQ0nmAgk-+B+HW88sNjztObtWwazof+cAGJGuuQ(a)mail.gmail.com>
GSoC: cache modelling plugin inquiry
Message-Id: <CAD-LL6hLk1XAB5VWwHgMOWQV=bT1+FCnf8f-q9MVw5e5A4RMqg(a)mail.gmail.com>
GSoC - QEMU Ideas
Message-Id: <CALpwMJz0kb2BDreTWBbt945FR+sLX=sKzHSv8pMb5LkLwXqEJA(a)mail.gmail.com>
Synced up with potential AGL Jailhouse/VirtIO GSoC applicant
Other
=====
- bit more write-up of blog post for [LBO-99]
[LBO-99] <https://projects.linaro.org/browse/LBO-99>
Completed Reviews [8/8]
=======================
[PATCH RESEND] docs: clarify absence of set_features in vhost-user
Message-Id: <20210325144846.17520-1-hi(a)alyssa.is>
[PATCH] docs: Add a QEMU Code of Conduct and Conflict Resolution Policy document
Message-Id: <72bc8020-2028-82db-219c-a6ae311e26df(a)redhat.com>
[PATCH v4 00/12] target/arm mte fixes
Message-Id: <20210406174031.64299-4-richard.henderson(a)linaro.org>
[PATCH 0/4] Acceptance Tests: update assets location and cancel tests if missing
Message-Id: <20200907042000.415931-1-crosa(a)redhat.com>
Added: <2020-09-07 Mon>
[RFC PATCH 0/3] tests/tcg/ppc64le: paddi tests
Message-Id: <20210415214138.563795-1-matheus.ferst(a)eldorado.org.br>
[RFC PATCH 00/15] gitlab-ci: Allow forks to use different pipelines than mainstream
Message-Id: <20210418233448.1267991-11-f4bug(a)amsat.org>
[PATCH 0/2] gdbstub: implement support for blocking interrupts on single stepping
Message-Id: <20210401144152.1031282-1-mlevitsk(a)redhat.com>
[PATCH v2 0/7] linux-user: sigaction fixes/cleanups
Message-Id: <20210422230227.314751-1-richard.henderson(a)linaro.org>
testing/next - hexagon toolchain update
Message-Id: <BN7PR02MB4194DF5752EF3BADE858018DB8799(a)BN7PR02MB4194.namprd02.prod.outlook.com>
[PATCH] tests/tcg: Run tests on arch variants again
Message-Id: <20210312152105.1836543-1-f4bug(a)amsat.org>
[PATCH 0/1] libbpf dependecy for docker containers.
Message-Id: <20210406082947.672708-1-andrew(a)daynix.com>
[PATCH v3 00/15] tests/tcg: Add TriCore tests
Message-Id: <20210305170045.869437-1-kbastian(a)mail.uni-paderborn.de>
Absences
========
Current Review Queue
====================
TODO [RFC PATCH v2 0/6] hw/arm/virt: Introduce cpu topology support
Message-Id: <20210413080745.33004-1-wangyanan55(a)huawei.com>
==============================================================================================================================
TODO [PATCH v2 00/12] virtio-gpu: Add support for Blob resources feature
Message-Id: <20210420065347.2685768-1-vivek.kasireddy(a)intel.com>
========================================================================================================================================
TODO [RFC v14 00/80] arm cleanup experiment for kvm-only build
Message-Id: <20210416162824.25131-1-cfontana(a)suse.de>
===================================================================================================================
TODO [PATCH v2 0/8] GICv3 LPI and ITS feature implementation
Message-Id: <20210401024152.203896-1-shashi.mallela(a)linaro.org>
===========================================================================================================================
--
Alex Bennée
Progress:
* UM-2 [QEMU upstream maintainership]
- code review:
+ Shashi's ITS emulation patchset
+ RTH's remaining fixes for MTE
+ RTH's patchset to implement alignment checking
- release work: sadly we found a pretty nasty crasher bug at the last
minute, so we'll release rc5 on Monday and final release Thursday
(with luck)
* QEMU-406 [QEMU support for MVE (M-profile Vector Extension; Helium)]
- useful discussions with RTH about how to implement MVE and in
particular how to handle its various flavours of insn predication
- some progress in writing code to implement the first insn (VLDR)
thanks
-- PMM
== Progress ==
* GCC upstream validation:
- Reported a few regressions
* GCC
- committed further fix for testcase for PR96770
- sent a few testsuite improvement patches
- resumed work on MVE/auto-vectorization. Added support for vcmp.f16.
Checking fp16 support in previous patches.
* Misc
- scripts patch reviews
== Next ==
* MVE auto-vectorization/intrinsics improvements
* GCC/cortex-M testing improvements & fixes
== Progress ==
* GCC upstream validation:
- Reported a few regressions
- Reduced build frequency on release branches, now same as trunk:
daily bump and arm/aarch64 "interesting" commits
* GCC
- pinged further fix for testcase for PR96770
- preparing cortex-m55 validation setup
- looking at cmse tests vs qemu
- Linaro BZ 5755/upstream 100049
* GDB
- uploaded cleaned up last known-to-work branch to sourceware so that
maintainers can have a look at it
- uploaded latest wip based on 8.2 branch too
* Misc
- scripts patch reviews
== Next ==
* MVE auto-vectorization/intrinsics improvements
* GCC/cortex-M testing improvements & fixes
Progress:
* UM-2 [QEMU upstream maintainership]
- Finished and posted patches implementing remap support for AN524
- Release work for rc3
- Sent a set of refactoring patches that split out some files we
were previously #including into translate.c so they are separate
compilation units.
- Thought a bit more about reset handling (in the course of writing
the AN524 remap patches I again ran into some of the deficiencies
of our current reset implementation; I really must take some time
this release cycle to try to improve things here...)
- Fixed bug where our AN547 board model accidentally disabled the FPU
on the Cortex-M55...
- ...and one where we were accidentally giving it an M33 rather than
an M55 !
- Respun and extended some patches from Paolo which fix our use of
QEMU and system headers in the 2 C++ files in the codebase (which
were broken by a change in new versions of glib)
- started looking at some of the for-6.1 patch review queue, which I
had been postponing in favour of for-6.0 stuff
* QEMU-406 [QEMU support for MVE (M-profile Vector Extension; Helium)]
- re-read the MVE portions of the v8M Arm ARM, sketched out a plan
of where to start with the QEMU implementation
thanks
-- PMM
https://gitlab.com/rth7680/qemu/-/commits/tgt-arm-bf16
It isn't a large extension, so all done. I added aarch64 simd, aarch32 neon,
and sve support all at once. I've tested it via risu vs FVP.
I've based this on my SVE2 branch, since there are some cleanups that made that
easier. I'll post patches to qemu-devel next week.
r~
== Progress ==
* GCC upstream validation:
- No regression to report this week. Issues on gcc-9 and gcc-10
release branches had already been reported by other people.
* GCC
- pinged further fix for testcase for PR96770
- Looking at failures for cortex-M, only found testisms so far
* Misc
- Fixed benchmarking jobs on stm32
== Next ==
* MVE auto-vectorization/intrinsics improvements
* GCC/cortex-M testing improvements & fixes
* Resume GDB/FDPIC work
VirtIO Initiative ([STR-9])
===========================
- had sync-up with Akashi-san/Vincent about approaches for the Zephyr
demo
- need to write-up on Monday
[STR-9] <https://projects.linaro.org/browse/STR-9>
QEMU Support for Xen ([STR-20])
===============================
- continued reviewing [RFC v12 00/65] arm cleanup experiment for
kvm-only build Message-Id: <20210326193701.5981-1-cfontana(a)suse.de>
- this is looking pretty solid now
- cut new version of [arm build clean-ups based on Claudio's series]
- testing reveals some breakage to track down next week
[STR-20] <https://projects.linaro.org/browse/STR-20>
[arm build clean-ups based on Claudio's series]
<https://github.com/stsquad/qemu/tree/xen/arm-build-cleanups-v3>
QEMU Upstream Work ([UM-2])
===========================
- posted [PULL 00/11] rc2 fixes (check-tcg, gitlab, gdbstub)
Message-Id: <20210406150041.28753-1-alex.bennee(a)linaro.org>
- some time trying to debug last weeks PR, eventually merged
[UM-2] <https://projects.linaro.org/browse/UM-2>
GSoC/Intern Mentoring
=====================
GSoC 2021 proposal initiation for AGL
Message-Id: <CAC+yH-Z_KZKuQ0nmAgk-+B+HW88sNjztObtWwazof+cAGJGuuQ(a)mail.gmail.com>
GSoC: cache modelling plugin inquiry
Message-Id: <CAD-LL6hLk1XAB5VWwHgMOWQV=bT1+FCnf8f-q9MVw5e5A4RMqg(a)mail.gmail.com>
GSoC - QEMU Ideas
Message-Id: <CALpwMJz0kb2BDreTWBbt945FR+sLX=sKzHSv8pMb5LkLwXqEJA(a)mail.gmail.com>
Synced up with potential AGL Jailhouse/VirtIO GSoC applicant
Completed Reviews [3/3]
=======================
[PATCH RESEND] docs: clarify absence of set_features in vhost-user
Message-Id: <20210325144846.17520-1-hi(a)alyssa.is>
[PATCH] docs: Add a QEMU Code of Conduct and Conflict Resolution Policy document
Message-Id: <72bc8020-2028-82db-219c-a6ae311e26df(a)redhat.com>
[PATCH v4 00/12] target/arm mte fixes
Message-Id: <20210406174031.64299-4-richard.henderson(a)linaro.org>
Absences
========
Current Review Queue
====================
TODO [RFC v12 00/65] arm cleanup experiment for kvm-only build
Message-Id: <20210326193701.5981-1-cfontana(a)suse.de>
==================================================================================================================
TODO [RFC 0/8] virtio: Improve boot time of virtio-scsi-pci and virtio-blk-pci
Message-Id: <20210325150735.1098387-1-groug(a)kaod.org>
===================================================================================================================================
TODO [PATCH 0/5] virtio: Implement generic vhost-user-i2c backend
Message-Id: <cover.1616570702.git.viresh.kumar(a)linaro.org>
===========================================================================================================================
TODO [PATCH v2 00/29] tcg: Workaround macOS 11.2 mprotect bug
Message-Id: <20210314212724.1917075-1-richard.henderson(a)linaro.org>
================================================================================================================================
--
Alex Bennée
Progress (short week, 2 days):
* UM-2 [QEMU upstream maintainership]
- more release work, bug triage, etc
- started implementing the memory-remapping feature of the
AN524 FPGA image (which allows the BRAM and QSPI to be swapped
either at startup or dynamically under guest control). Some guests
(like ARM TF-M) assume the QSPI mapping.
thanks
-- PMM
== Progress ==
* GCC upstream validation:
- Reported minor testsuite issues (eg failures with -mabi=ilp32 on aarch64)
- re-started looking at validation for cortex-m55, realized that qemu
does not support MVE yet
* GCC
- posted further fix for testcase for PR96770
- fixed PR 99786
- committed fix for PR 99773
* Misc
== Next ==
* MVE auto-vectorization/intrinsics improvements
* GCC/cortex-M testing improvements & fixes
* Resume GDB/FDPIC work
Progress:
* UM-2 [QEMU upstream maintainership]
- tagged rc0
- various bug investigation/patches for 6.0-ish stuff:
+ machines with a 'platform bus' incorrectly treated all sysbus
devices as hotpluggable: wrote and sent patchseries
+ respin of gpex pci-host "don't fault for unmapped MMIO/PIO window
accesses" patch
+ document how to use gdbstub/gdb for a multi-cluster machine where
the clusters are different gdb inferiors
+ looked for workarounds for macos Appkit bug where Apple broke menubars
for apps that start off as console apps and programmatically switch
themselves to being GUI apps; various online suggestions don't seem
to help, except for "when app starts, force the Dock to become active
and then grab back focus 200ms later". Maybe we'll do that, but it's
pretty ugly...
thanks
-- PMM
== Progress ==
* GCC upstream validation:
- Small improvement to pre-commit testing scripts to allow running a
subset of the tests (and thus save a lot of time)
* GCC
- MVE autovectorization:
- vcmp support of FP types OK.
- testsuite cleanup: looking at current failures, only found issues
with tests so far. Testing several small testsuite patches is taking a
long time due to the number of configurations
* Misc
== Next ==
* MVE auto-vectorization/intrinsics improvements
* GCC/cortex-M testing improvements & fixes
* Resume GDB/FDPIC work
Progress:
* UM-2 [QEMU upstream maintainership]
- softfreeze was this week, lots of pullreq processing
- spun v2 of "fix M-profile load of PC/SP from ELF images via
memory aliases"
thanks
-- PMM
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
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.
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
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.
[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~
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
Hi, all
Does anybody know what does '.....isra.0' mean in GCC 10.2 compiled objects?
I just noticed this issue when using bcc/eBPF tools. I submitted the detail
into
* https://github.com/iovisor/bcc/issues/3293
Simply put, when building a linux kernel with GCC 10.2, the symbol
'finish_task_switch' becomes 'finish_task_switch.isra.0' in the object (as
reported by 'nm')
Because a lot of kernel tracers (such as bcc) use 'finish_task_switch' as
the probe point, this change in the compilation result can make all result
such tools fail.
Thanks.
Best regards,
Guodong Xu
== Progress ==
* GCC upstream validation:
- a couple of regressions to bisect.
- minor testcase fix
- reported a couple of new failures
* GCC
- MVE autovectorization:
- vcmp support mostly complete. Minor update needed to support FP types.
- working on interleaved vector load/store support
* Misc
- fixed stm32 benchmarking harness, it's working again.
- submitted patches to reduce the toolchain build time (for
benchmarking we don't need all multilibs which take ages to build)
== Next ==
* MVE auto-vectorization/intrinsics improvements
* GCC/cortex-M testing improvements & fixes
* cortex-m benchmarking
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.
Hi,
I've been trying to use clang on Windows on Arm machine (Samsung Galaxy Book S), but whenever I try to use it, I get either nothing (in powershell) or an error popup: "The application was unable to start correctly (0x000007b)".
The release I'm using is LLVM-12.0.0-rc1-woa64.exe<https://github.com/llvm/llvm-project/releases/download/llvmorg-12.0.0-rc1/L…> from https://github.com/llvm/llvm-project/releases/tag/llvmorg-12.0.0-rc1
I have a feeling there might be a library or dependency I am missing.
Any help with how to resolve this issue would be appreciated.
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.
[UM-2 # QEMU Upstream Work]
* A lot of patch review.
* Some target/i386 cleanup, as followup to said patch review.
* Collecting patches for tcg-next.
r~
== Progress ==
* GCC upstream validation:
- a few regressions to bisect. Fixed a minor testcase issue
* GCC
- MVE autovectorization: Working on vcmp. After some cleanup &
factorization, the cmp operators work on GCC vectors. I will now
resume work on auto-vectorization.
* Misc
- fixes in stm32 benchmarking harness
== Next ==
* MVE auto-vectorization/intrinsics improvements
* GCC/cortex-M testing improvements & fixes
* cortex-m benchmarking
* After proving that the aarch64 host problem with
booting s390x with virtio was lack of barriers for
the guest memory model, I've spent some time working
on a ld-acq/st-rel optimizer for tcg.
* Minor rev of tci rewrite.
* Some patch review on claudio's kvm/tcg split.
r~
Progress:
* QEMU-364 [QEMU support for ARMv8.1-M extensions]
+ sent out v2 of the MPS3-AN524 series (minor changes only)
+ discovered that I need to implement the SSE-300's System Counter
+ implemented the system counter, did some final testing and
reviewing, and sent out v1 of the MPS3-AN547 series to the list
+ once these patches are reviewed and in master the QEMU-413 epic
will be complete
-- PMM
Hello Linaro Toolchain Working Group,
libcxx-libcxxabi-libunwind-armv8-linux has been red for 5 days.
clang-cmake-aarch64-global-isel has been red for 10 days.
clang-cmake-aarch64-quick has been red for 10 days.
clang-cmake-armv7-global-isel has been red for 10 days.
clang-cmake-armv7-lnt has been red for 10 days.
clang-cmake-aarch64-lld has been red for 11 days.
clang-cmake-armv8-lld has been red for 11 days.
clang-cmake-thumbv7-full-sh has been red for 11 days.
clang-cmake-armv7-full has been red for 11 days.
Is anybody looking at this?
I also noticed that some of your workers are less reliable than others. For
example, inaro-tk1-09 worker was last time producing a green build 2 months
ago - http://lab.llvm.org:8011/#/workers/2?numbuilds=500
I'm removing the linaro-tk1-09 worker from the production buildbot for now.
Please feel free to connect it to the staging and make the builder reliably
green. Then it could be returned back to the production.
linaro-armv8-windows-msvc-01 and linaro-armv8-windows-msvc-02 have been red
for the least 4 months. I'm removing them from the production buildbot. You
can return them back to production after they are reliably green in the
staging.
Please feel free to ask if you have questions.
Thanks
Galina
== Progress ==
* GCC upstream validation:
- a few regressions to bisect. Fixed a minor testcase issue
- native validation in Linaro's lab: we still see a few random results
* GCC
- MVE autovectorization: Working on vcmp.
* Misc
- fixes in stm32 benchmarking harness
== Next ==
* MVE auto-vectorization/intrinsics improvements
* GCC/cortex-M testing improvements & fixes
* cortex-m benchmarking
Holidays next week, back Monday 22nd Feb
Progress:
* UM-2 [QEMU upstream maintainership]
+ sent out a small code-cleanup patchset for some arm display device
models to remove no-longer-needed support for non-32bpp outputs
+ tracked down (with the aid of Paolo) why our build system had started
building the documentation every time you run 'make'; sent a fix
+ code review todo queue status: 12 items, but the oldest was only
sent to the list on Monday...
* QEMU-364 [QEMU support for ARMv8.1-M extensions]
+ An MPS3 Cortex-M55 FPGA image is now publicly available: the AN547.
We'll provide a model of this in QEMU. Started working on the
patchseries to implement it (relatively small changes on top of
the SSE-300 work I've already done but not sent out, and the
mps3-an524 series I sent out for review last week). This is basically
code-complete but I need to do some more testing and ideally I'd
like the AN524 series to get reviewed before I send out another
40-patch series that would have to be based on top of that one.
thanks
-- PMM
Hello,
I've uploaded binaries for Windows on Arm:
081373cc76e88224020fea42eba2161d972f03bb83ebc055fb3cd4f2cfcdfb95
LLVM-12.0.0-rc1-woa64.exe
It was built from the current release/12.x branch (commit b46924ee) with
two patches applied on top:
- https://reviews.llvm.org/D96259
- https://reviews.llvm.org/D96498
It contains "clang;clang-tools-extra;lld;compiler-rt” projects.
Compiler-RT has sanitizers disabled (MEMPROF and XRAY use sanitizer
infrastucture). I.e.,
===
+ -DLLVM_ENABLE_PROJECTS="clang;clang-tools-extra;lld;compiler-rt" ^
+ -DCOMPILER_RT_BUILD_SANITIZERS=OFF ^
+ -DCOMPILER_RT_BUILD_MEMPROF=OFF ^
+ -DCOMPILER_RT_BUILD_XRAY=OFF ^
===
I've attached the changes we had to make to
llvm/utils/releases/build_llvm_package.bat. @Maxim Kuvyrkov is going to
clean them up and post a patch in the next couple of weeks (he's been doing
all the hard work, I'm just uploading).
This is the first time we're trying to provide a release for Windows on
Arm, so if anyone has any comments or questions, feel free to send an email
:)
Cheers,
Diana
On Thu, 28 Jan 2021 at 05:05, Tom Stellard via lldb-dev <
lldb-dev(a)lists.llvm.org> wrote:
> Hi,
>
> I've tagged the 12.0.0-rc1 release. Testers can begin testing and upload
> binaries.
>
> -Tom
>
> _______________________________________________
> lldb-dev mailing list
> lldb-dev(a)lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
VirtIO Initiative ([STR-9])
===========================
- TSC Stratos next cycle presentation
- [Stratos Sync - this week discussing Rust]
- Followed up on Rust presentation and sketched out some areas of
interest
[STR-9] <https://projects.linaro.org/browse/STR-9>
[Stratos Sync - this week discussing Rust]
<https://collaborate.linaro.org/display/STR/2021-02-04+Project+Stratos+Sync+…>
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
- bunch of related review of pre-cursor stuff
[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])
===========================
- caught up on a bunch of review
- got about halfway through rth's mega TCI series
- posted [PATCH v1 00/15] testing/gdbstub/docs pre-PR Message-Id:
<20210202134001.25738-1-alex.bennee(a)linaro.org>
- will roll PR on Monday
- some discussion on Detecting Faulting Instructions From Plugins
Message-Id: <YBTRSK4/F5KLH+FZ(a)strawberry.localdomain>
- looks like we need special handling for instrumentation on
recompiled IO ops
[UM-2] <https://projects.linaro.org/browse/UM-2>
Completed Reviews [5/5]
=======================
[PATCH 00/10] target: Provide target-specific Kconfig
Message-Id: <20210131111316.232778-1-f4bug(a)amsat.org>
[PATCH v3 0/5] Fix some style problems in contrib
Message-Id: <20210118031004.1662363-1-zhouyang789(a)huawei.com>
[PATCH v15 00/23] i386 cleanup PART 2
Message-Id: <20210201100903.17309-1-cfontana(a)suse.de>
[PATCH 00/22] Acceptance Test: introduce base class for Linux based tests
Message-Id: <20210203172357.1422425-9-crosa(a)redhat.com>
[PATCH v2 0/5] Move remaining x86 Travis jobs to the gitlab-CI
Message-Id: <20210205091857.845389-1-thuth(a)redhat.com>
Absences
========
- Lockdown 3: Home schooling returns!
Current Review Queue
====================
* [PATCH v6 00/11] Support disabling TCG on ARM (part 2)
Message-Id: <20210131115022.242570-1-f4bug(a)amsat.org>
Added: <2021-01-31 Sun>
* [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>
--
Alex Bennée
== Progress ==
* GCC upstream validation:
- not really catching up, now ~15 days late due to the numerous
commits. Manually fast-forwarded the latest build to today. I'll
bisect manually for regressions if needed.
- re-enabled native validation in Linaro's lab: we are sending test
results again
* GCC
- MVE autovectorization: vorn patch committed. Working on vcmp.
== Next ==
* MVE auto-vectorization/intrinsics improvements
* GCC/cortex-M testing improvements & fixes
* cortex-m benchmarking
Progress:
* UM-2 [QEMU upstream maintainership]
+ lots of code review this week, including another round of rth's
MTE user-mode patchset
* QEMU-364 [QEMU support for ARMv8.1-M extensions]
+ Sent out an RFC proposing some more Clock API changes (since it'll
be a while before I'm ready to post the series with the new timer
device that requires them)
+ The SSE-200 Cortex-M33-based MPS3 AN524 FPGA image is a useful
target to model: the Zephyr folks would like it, and it is a good
stepping stone to an MPS3 FPGA image with a Cortex-M55/SSE-300 in
it. Wrote a patchset for an mps3-an524 board model, and sent it out
for review.
-- PMM
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