Many thanks for the comprehensive reply, Thiago.
As it happens, running valgrind with -s on both new testcases, indicates
problems emanating from one line in the other test,
class_transformational_1.f90. I am investigating and will put it right.
Regards
Paul
On Tue, 9 Jul 2024 at 04:13, Thiago
Hello Paul,
Paul Richard Thomas writes:
> Thank you very much for your debugging efforts. You really pulled out the
> stops.
You're welcome. In the future if there are other issues or questions
regarding our CI, please feel free to contact us.
> Can I take it then that you will update the too
Hi Ulf,
Indeed, this report is for building binutils with only 2 first patches applied.
Patch #3 fixes this failure; see
https://patchwork.sourceware.org/project/binutils/list/?series=35932 .
However, the point of our CI testing "incomplete" patch series is to catch
cases when a problem is in
I get this problem when the CI is building a patchset for the binutils
with my patches.
The patchset consists of 7 patches, and I suspect that this error message
is generated when only part of the 7 patches are applied.
Could this be true?
They are interdependent, so there is no way to reorder
