From: Richard Biener <rguenther@suse.de>
To: "René Rebe" <rene@exactcode.de>
Cc: gcc@gcc.gnu.org, Frank Scheiner <frank.scheiner@web.de>
Subject: Re: Stepping up as maintainer for ia64
Date: Thu, 7 Mar 2024 20:08:34 +0100 [thread overview]
Message-ID: <A935D68A-1B29-421A-A239-52CA50ADA239@suse.de> (raw)
In-Reply-To: <45833A6D-A84C-4276-AADB-BE2923886F64@exactcode.de>
> Am 07.03.2024 um 19:09 schrieb René Rebe <rene@exactcode.de>:
>
> Hey there,
>
> I saw the deprecation of ia64*-*-* scrolling by [1].
>
> Which surprised me, as (minor bugs aside) gcc ia64*-*-linux just works for us and
> we still actively support it as part of our T2 System Development Environment [2].
>
> For ia64 we are currently a team of three and also keep maintaining linux-kernel and
> glibc git trees with ia64 restored and hope to bring back ia64 to linux upstream the
> coming months as promised. [3]
>
> Despite popular believe ia64 actually just works for all those projects and we already
> fixed the few minor bugs we could find or reproduce.
>
> Last week I also already patched and tested enabling LRA for ia64 in gcc [4] and could
> -without any regression- compile a full ia64 T2/Linux release ISO that boots and runs
> including an X desktop and Gtk applications. That was of course even with the latest
> linux kernel and glibc versions with ia64 support restored respectively.
>
> Given there are currently no other volunteers, I therefore with this email step up and
> offer to become ia64 maintainer for GCC to keep the code compiling, tested and
> un-deprecated for the next years and releases to come.
You’re welcome - we look forward to LRA enablement with ia64 and for it to get an
active maintainer. Note maintainers are appointed by the Steering Committee.
If I read you correctly you’d keep the ia64-Linux port alive but the other sub-architectures like the hpux port can remain deprecated?
Thanks,
Richard
> Thank you so much,
> René Rebe
>
> [1] https://inbox.sourceware.org/gcc-bugs/bug-90785-4-X7KYh6SLIg@http.gcc.gnu.org%2Fbugzilla%2F/T/
> [2] https://t2sde.org/#news-2023-12-05
> [3] https://lore.kernel.org/linux-ia64/CAHk-=whFLZ67ffzt1juryCYcYz6eL_XjQF8WucDzwUR5H65+rA@mail.gmail.com/
> [4] https://svn.exactcode.de/t2/trunk/package/develop/gcc/ia64-lra-impl.patch
>
> --
> ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin
> https://exactcode.com | https://t2sde.org
next prev parent reply other threads:[~2024-03-08 6:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 17:52 René Rebe
2024-03-07 19:08 ` Richard Biener [this message]
2024-03-08 8:54 ` René Rebe
2024-03-08 13:16 ` Richard Biener
2024-03-08 22:00 ` Peter Bergner
2024-03-08 22:31 ` Frank Scheiner
2024-03-08 23:28 ` Jonathan Wakely
2024-03-09 2:18 ` Peter Bergner
2024-03-09 17:08 ` Frank Scheiner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A935D68A-1B29-421A-A239-52CA50ADA239@suse.de \
--to=rguenther@suse.de \
--cc=frank.scheiner@web.de \
--cc=gcc@gcc.gnu.org \
--cc=rene@exactcode.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).