> > One thing we could do to remove fragility in the test is to remove the
> > running of `short.py` in the test. This is only invoked to check that
> > it's possible for a command to run to completion in the presence of a
> > fixed timeout. If we can live without testing that part (i.e. we only
>
== Progress ==
* GCC upstream validation:
- reported several regressions
- committed minor cleanup fixes
- improved gcc-testresults email titles after discussion with other contributors
* GCC
- PR96767: patch sent
- PR96770: patch sent
- sent another patch to fix C++ thunks with -mpure-code and c
