Re: Stepping up as maintainer for ia64

[Frank Scheiner <frank.scheiner@web.de>]

On 08.03.24 23:00, Peter Bergner wrote:
> On 3/8/24 7:16 AM, Richard Biener via Gcc wrote:
>> I CCed Jeff who is on the commitee to forward the maintainer proposal
>> though I guess this will not go forward as a first step.  Instead
>> you are probably expected to show activity on the port, for example
>> post the patch series to make ia64 use LRA, get write access to the
>> git repository and then be promoted maintainer.
>
> One other method for showing activity is posting regular testsuite
> results on the gcc-testresults mailing list to show the community
> the port is "working".

I don't want to spam this or the other list each and every week, but I
am since a while cross-compiling each Linux mainline RC and release with
the latest gcc-14 snapshot available each time and test the result on a
variety of real machines and on the HP Sim platform in Ski (since
recently). And since doing that I haven't seen any new ICEs since I
reported [1].

[1]: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111425

Something similar is done automatically for the Linux stable RC and
releases but with a fixed gcc-13.2.0 cross-compiler (provided by Arnd
Bergmann on [2]) on GitHub, including a test run in Ski, see for example
[3].

[2]: https://mirrors.edge.kernel.org/pub/tools/crosstool/

[3]:
https://github.com/johnny-mnemonic/linux-stable-rc/actions/runs/8198165399

Both are surely not as extensive as a testsuite run, but give a good
preview I think: it's working for what we are doing with these machines,
thanks for asking.

Cheers,
Frank