Hello,
# TCWG CI — GDB
- Addressed review comments and sent v2 and v3 of the patch fixing loop
in gdb.reverse/step-reverse.exp. The testcase's original author gave his
Reviewed-by, now waiting for approval by a maintainer. In the meantime,
set up our CI to apply the patch locally.
- Sent patch to the GDB mailing list implementing configure option
'--with-additional-debug-dirs' to allow building a GDB binary with a
custom install prefix but which also looks for debug info in
/usr/lib/debug. This should solve the SIGILL issue on armhf-linux in our
CI, and allow a few more tests to run on aarch64-linux.
# TCWG Infrastructure
- Reviewed some Gerrit requests related to notification and baseline
updating.
--
Thiago
Hello,
# TCWG CI — GDB
- Continued investigating issue with GDB on armhf-linux about getting
SIGILL when trying to detect shared library loading/unloading. Noticed
that the problem happens only in tests that use the distro's toolchain
(either because they're for a language we don't build in ABE gcc, or
because GDB itself is built with the distro toolchain), so the impact
isn't as widespread as I initially thought. It still frequently causes
trouble for our CI loop though. Working on a fix.
- Investigated and fixed loop in gdb.reverse/step-reverse.exp that was
causing tcwg_gdb_check--master-arm-build jobs to get stuck, as
reported by Maxim. Posted patch to the GDB mailing list.
# TCWG Infrastructure
- Reviewed Gerrit requests about testing mailing list patches in our CI.
--
Thiago
Progress (another short week, May is great this year):
* UM-2 [QEMU upstream maintainership]
- More review on some of RTH's atomics related patchsets
- Put together an arm pull request
- Sent out a call for agenda items for QEMU Summit
* QEMU-530 [QEMU ARM v9.4 Baseline CPU for TCG]
- decodetree load/store conversion done, patches sent out for review.
After this I plan to go back to the FEAT_MOPS implementation
(and then do the last part of the integer A64 decodetree
conversion later in this release cycle).
-- PMM
Hello,
# TCWG CI — GDB
- Investigating issue in CI jobs where touching all C files causes GDB
to show a warning about the source being newer than the executable.
This interferes with a few GDB tests.
- Continued investigating issue with GDB on armhf-linux about getting
SIGILL when trying to detect shared library loading/unloading. Found
out that the GDB testsuite binaries are using the distro's ld.so
rather than the one built by ABE and which is the one expected to be
used. Because we don't have debuginfo installed for the distro's
ld.so, we hit the GDB bug in armhf-linux. The ld.so built by ABE has
debuginfo and would avoid hitting the issue.
# TCWG Infrastructure
- Reworked CI job to sanity check tcwg_gnu_fast_check_{gcc,gdb} and
posted new version for review.
- Reviewed some Gerrit requests for jenkins-scripts and ABE.
--
Thiago
Progress (short week, three days):
* UM-2 [QEMU upstream maintainership]
- Sent a patch fixing a bug where we broke some M-profile uses
(resulting in assertion failures) when we added v8R support
* QEMU-530 [QEMU ARM v9.4 Baseline CPU for TCG]
- Implemented support for a new feature in the decodetree
generator that I need for the A64 decodetree conversion,
sent patches out for review
- More progress on A64 decodetree: loads and stores
-- PMM
Hello,
# TCWG CI — GDB
- Analysed a number of potential regressions found by our CI on
aarch64-linux and armhf-linux. They aren't exactly regressions but bug
fixes or new features that work on other arches (or perhaps whose
testcases correctly detect PASSes on other arches) but not on
aarch64-linux or armhf-linux.
- armhf-linux has an important problem where a bug with detecting shared
library loading/unloading is causing many tests to fail. The result is
that every new GDB commit that adds a test is flagged by the bisect
job. This was caused by a GDB commit from November 2022. Luis reported
it at the time and the patch author was going to look into it, but
this probably fell through the cracks. I'm investigating to understand
the problem better and provide a fix.
--
Thiago
Progress:
* UM-2 [QEMU upstream maintainership]
- Reviewed another round of RTH's patchset overhauling atomics
- Sent an arm pullreq
* QEMU-530 [QEMU ARM v9.4 Baseline CPU for TCG]
- Continued with the conversion of the A64 decoder to decodetree:
have converted hints, barriers, system register insns,
exception generation, and am halfway through the loads and stores.
-- PMM
Hi,
Has anyone noticed that https://lab.llvm.org/buildbot/#/builders/198 (clang-aarch64-sve-vla-2stage<https://lab.llvm.org/buildbot/#/builders/198>) has been timing out for the past few days? "Duration" is often less than 1hr, so that's odd. And all Flang buildbots are green, so it's unlikely caused by changes to that sub-project (https://lab.llvm.org/buildbot/#/builders/198/builds/1804). Would anyone be able to take a look?
Best regards,
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.
Hello,
# TCWG Infrastructure
- Reviewed a bunch of Gerrit requests for our CI scripts.
- Finished job definition to run fast_check_{gcc,gdb} jobs triggered by
new Gerrit review requests for jenkins-scripts, benchmark scripts and
ABE. Sent Gerrit review request and now working on 2nd version.
- Rebased our DejaGNU debug patches to upstream dejagnu-1.6.3, tested
result and sent Gerrit review request for it.
# TCWG CI — GDB
- Confirmed regression found by CI job¹ and mentioned by Maxim. Found
out that it was fixed upstream already².
--
Thiago
¹ https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-bisect/…
² https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5a6ad5c775a58367…
Progress (another short week, May is full of bank holidays :-)):
* UM-2 [QEMU upstream maintainership]
- usual background level of code review etc
- investigated a bug reported by Mozilla where people running x86 Firefox
on QEMU on Arm hardware were seeing crashes; narrowed down the cause
(aided by Mozilla kindly providing a minimal repro test case),
and Paolo produced a fix.
* QEMU-530 [QEMU ARM v9.4 Baseline CPU for TCG]
- Started looking at what is required for FEAT_MOPS (the
memcpy/memset/memmove insns), what they do and how QEMU ought
to implement them.
- The new insns are in the load/store part of the A64 instruction
space. To make this easier to do, we should really convert at
least the integer parts of the A64 decoder to decodetree (a
refactoring we've been putting off for a long time). Started on
the conversion: sent out a first 20-patch patchset that converts
the dp-immediate and branch insns.
-- PMM
Progress (combines two weeks):
* UM-2 [QEMU upstream maintainership]
- investigated various failures of avocado tests on s390x host.
These are at least four different unrelated endianness bugs in
different device, board or CPU models. Sent out a set of patches
fixing at most of these.
- TCWG / Arm syncup meeting
- Linaro Connect
- caught up on code review and sent a target-arm pull request
- sent patch fixing a bug where our PNG screenshots have the pixel
colour channels in the wrong order
- while I had a conversation from Connect fresh in my mind, went
back and re-looked at the page-table-walk bug with handling the
NSW/SW bits that I sent patches for a couple of weeks ago. Re-did
the code to consistently handle these bits in the right place and
sent out another version of the patchset
- reviewed a very large patchset from RTH that changes how
TCG handles atomic accesses so we can implement FEAT_LSE2
- investigated a bug report about a regression with AArch32 EL1
under an AArch64 EL2; wrote patch
-- PMM
Hello,
# TCWG Infrastructure
- Reviewed a bunch of Gerrit requests for our CI scripts.
- Learning Jenkins job builder syntax and working on a job definition to
run fast_check_{gcc,gdb} jobs on Gerrit review requests for
jenkins-scripts and ABE.
- Changed CI scripts to save ABE and component testsuite logs when the ABE
build or check step fails. This should help debug a case where a GDB CI
job failed due to (probably) a corruption of the gdb.sum testsuite
result file.
# Misc
- Some preparations for the trip to Linaro Connect.
--
Thiago
Progress:
* UM-2 [QEMU upstream maintainership]
- sent out v3 of the 'deprecate singlestep option' patchset
- sorted out the draft QEMU Summit invite list and invitation text
- spent some time trying to understand how the imx SoCs arrange
their ethernet controllers and PHYs so I can review a patchset
- sent patch fixing minor configure nit where it wasn't honouring
--cross-prefix for the ObjC compiler
- got the 8.0 release out of the door and handed over merge handling
to rth
- sent some patchsets updating a few old .txt files to reStructuredText
- still thinking about our page-table-walk code -- I'm not convinced
it's doing the right thing with NSW/SW bits, even after last
week's patchset...
-- PMM
Hello,
# TCWG Infrastructure
- Fixed problem in ABE with MinGW build of GDB's master branch.
- Fixed problem in upstream GDB with MinGW build of GDB's master branch.
- Analysed backlog of failed check_gdb jobs.
- A couple of "misbisected" commits, including one pointing to a glibc commit.
- One detected regression also noticed by Christophe, and fixed by the community.
- One Arm failure that passes on QEMU TCG.
- Reviewed a number of Gerrit requests about improving ABE and CI scripts.
--
Thiago
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
