Progress:
* UM-2 [QEMU upstream maintainership]
* trying to get a release out of the door -- due among other things
to the Easter holiday weekend, rc4 is a bit late and has rather
more changes than I would prefer
* more triaging of Coverity issues
* sent a few trivial bug fix patches
* started reviewing and queueing arm patches for 8.1
* investigated a FEAT_SEL2 bug that showed up with some proposed
changes to TF-A/Hafnium. The architecture and QEMU's code
are pretty hairy in this area but I think I have identified
the correct fix...
-- PMM
Hello,
[GNU-796] Stabilize GDB testsuite results in the CI
- Submitted to GDB mailing list and committed patches fixing the
gdb.asm/asm-source.exp regression found by the check_gdb job. Turned out
to be a small bug in the stabs debug format support.
- Committed Gerrit review request disabling Python on MinGW cross builds.
[GNU-767] Support changing SVE vector length in remote debugging
- Investigating a follow-up question Simon asked during review of the
patch series fixing a corner case when reading auxv from multi-threaded
inferiors.
--
Thiago
Progress:
* UM-2 [QEMU upstream maintainership]
* rc3 this week
* reworked my "deprecate the misleading -singlestep option"
patchset to deal with review feedback, sent out v2
* KVM Forum programme committee work
* investigated a regression where the mps3-an547 board
asserts on startup; for 8.0 we will just revert the change
that introduced the failure, since it was only an optimization
* some triage of Coverity issue reports; sent some patches for
some easy ones, queried original code submitter for others
-- PMM
Hi Alexandros,
Linaro benchmarking CI flagged this patch. After it clang seems to miscompile 602.gcc_s from SPEC CPU2017 for "-O3 -flto" on aarch64-linux-gnu. Also, it appears that 600.perlbench_s slows down by 9%.
Could you investigate, please? Let me know if you need any assistance in reproducing the problem.
Our Benchmarking CI is still in active development, and there are false positives, but this report seems to be legit [1].
Kind regards,
[1] https://ci.linaro.org/job/tcwg_bmk-code_speed-cpu2017speed--llvm-aarch64-ma…
--
Maxim Kuvyrkov
https://www.linaro.org
Hello,
[GNU-796] Stabilize GDB testsuite results in the CI
- Committed ABE change suggested by Maxim to mention failures that cause
additional testsuite runs.
- Tried to update Python MinGW build to 3.x, but it's a rabbit hole.
Proposing to disable Python support when cross-building GDB with MinGW
instead.
- First regression detected by the tcwg_gnu_native_check_gdb CI job
reported upstream¹. Started investigating it.
[GNU-767] Support changing SVE vector length in remote debugging
- Created a testcase to exercise the corner case mentioned by Pedro.
Found out that GDB is also susceptible to it. Fixed both GDB and
gdbserver. Posted patch series upstream².
--
Thiago
¹ https://inbox.sourceware.org/gdb-patches/871ql6dhf4.fsf@linaro.org/
² https://inbox.sourceware.org/gdb-patches/20230331034432.3037148-1-thiago.ba…
Progress (short week, holiday and recovering from covid...):
* UM-2 [QEMU upstream maintainership]
* 8.0 release related work rumbles on
* debugged and fixed a regression caused by my work on HSTR_EL2 traps
* QEMU-530 [QEMU ARM v9.4 Baseline CPU for TCG]
* implemented FEAT_PAN3 (and fixed a minor bug in
syndrome reporting that I noticed in the process)
-- PMM
Hello,
[GNU-796] Stabilize GDB testsuite results in the CI:
- Enabled gdb.gdb/unittest.exp in fast_check_gdb job. It should be
stable now that tcwg-jade-02's kernel has been upgraded.
- Enabled bisections for check_gdb jobs.
- Implemented Maxim's idea to handle GDB testsuite's tests that can FAIL
but are silent when they pass (i.e., the "gdb_test -nopass"
statements).
[GNU-767] Support changing SVE vector length in remote debugging
- Back in February I upstreamed a couple of preparation patches and
Pedro noticed an unintended change in behaviour that can affect a
corner case, so I am working on a fix for that now.
--
Thiago
