Progress:
* UM-2 [QEMU upstream maintainership]
- release related stuff: handling merge requests, etc (now passed
back to RTH again)
- sent some patches for a few easy coverity issues
- worked through some code review (in particular some patches
from new contributors)
- created a gitlab "bite sized task" issue that better explains
and has more detail on the "convert from malloc to g_malloc"
suggested task for new contributors
* QEMU-530 [QEMU ARM v9.4 Baseline CPU for TCG]
- a little more progress with FEAT_MOPS. I now have an untested
implementation of the memset insns which I think is complete
except for MTE tag checking
-- PMM
Hello,
# TCWG CI
- Babysat the CI: Investigated 9 regressions in GCC, 2 in GDB, 1 in LLVM
and 1 in glibc. Reported 4 in GCC (GNU-855, GNU-857, GNU-858 and
GNU-859). 3 of which are fixed and another has a tentative fix.
- Reviewed a couple of Gerrit requests.
--
Thiago
Progress:
* UM-2 [QEMU upstream maintainership]
- fixed some places in our RTC device models where we were
putting a time_t or time_t offset into a 32-bit variable
- took over from RTH briefly for pullreq merge handling
- sent some patches fixing minor Coverity issues
- investigated a couple of "test case fails on big-endian host"
errors: sent patches for Sparc FPRS handling and for
the Arm SMMUv3 model
- Investigated report that our MPS2/3 M-profile models don't
have the same number of MPU regions configured as the real FPGA
images, and so you can't run the same Zephyr binary on both.
Have some preliminary patches to correct the number of regions.
* QEMU-530 [QEMU ARM v9.4 Baseline CPU for TCG]
- finally got back to FEAT_MOPS work; wrote a skeleton of code
for the memset operations that's about right up to the point
where it needs to actually do the memset...
-- PMM
Hi everyone,
I'm not 100% sure whether this is a bot misconfiguration issue, but couldn't find any other source of this failure:
```
******************** TEST 'test-suite :: MultiSource/Applications/ClamAV/clamscan.test' FAILED ********************
Executable '/home/tcwg-buildbot/worker/clang-aarch64-sve-vla/test/sandbox/build/MultiSource/Applications/ClamAV/clamscan' is missing
********************
```
Link: https://lab.llvm.org/buildbot/#/builders/197/builds/8209
Would anyone be able to take a look?
Thank you :)
-Andrzej
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]
- investigated and fixed a bug in page-table-walk handling of
debug accesses that was introduced by the FEAT_RME changes
- that prompted me to look at a cleanup of some of the ptw code
so that we consistently look at "which space is this walk for"
and don't carry around a parallel boolean "secure/non-secure"
that duplicates that information
- found and fixed a few other ptw bugs along the way
-- PMM
Hello,
# TCWG CI
- Changed tcwg_gnu-build.sh to apply GDB patch adding
'--with-additional-debug-dirs' option, and ABE's gdb.conf to use it.
Also changed both to add '--prefix /usr' option to GDB's configure.
Both changes to fix ld.so debug info issues in GDB testsuite runs on
armhf.
- Testing changes to validate_failures.py and jenkins-scripts to handle
empty gdb.sum.
- Reviewed a few Gerrit requests.
--
Thiago
Progress (short week, 3 days):
* UM-2 [QEMU upstream maintainership]
- softfreeze is next week, so spent some time putting together
a pull request, fixing the bugs which the CI tests found in
it, etc
* QEMU-422 [QEMU Arm Neoverse V1 vCPU for TCG]
- now that we implement all the necessary features (excluding
some trace/profiling type stuff that is out-of-scope for
QEMU, and also FEAT_NV that we might come back to later), sent
out the patchset to define a 'neoverse-v1' CPU type for QEMU
-- PMM
Hello,
# TCWG Infrastructure
- Investigated why the CI didn't recover from empty gdb.sum, since it
was supposed to.
- Fixing validate_failures.py and tcwg_gnu-build.sh to correctly handle
empty gdb.sum.
- Fixing GDB armhf CI jobs to find distro's debug info.
# CI Babysitting
- Verified that a couple of regressions I reported last week were fixed
in trunk.
--
Thiago
