From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: "Maciej W. Rozycki" <macro@embecosm.com>
Cc: gcc@gcc.gnu.org, Matt Thomas <matt@3am-software.com>,
Matt Thomas <matt@netbsd.org>,
"Maciej W. Rozycki" <macro@orcam.me.uk>
Subject: Re: VAX/GCC port maintenance
Date: Thu, 21 Oct 2021 10:12:11 +0200 [thread overview]
Message-ID: <20211021081211.olbykryeu4umpsrh@lug-owl.de> (raw)
In-Reply-To: <alpine.DEB.2.20.2110181209480.17921@tpp.orcam.me.uk>
[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]
Hi Maciej,
On Tue, 2021-10-19 15:39:15 +0100, Maciej W. Rozycki <macro@embecosm.com> wrote:
> I have recently started a new position at Embecosm and the company has
> offered me to sponsor a personal project related to its business. So I
> had it in my mind already for a while to continue the effort with the VAX
> backend I have started with the MODE_CC conversion, as a port maintainer.
I'm all for it!
> There has been the outstanding issue of improving code generation with
> LRA we are going to switch to sometime as well as other problems noticed
> in the course of said conversion. I will be happy to look into all this
> and more for the port to improve and I seem to have been the only person
> making substantial changes to the port in the recent times. And I can
> serve as the point of contact for any queries or discussions about the
> port.
>
> Would the GCC steering committee be willing to hand this responsibility
> over to me?
As well: I'm all for it! In the last few years, only minimal
maintenance happened for the VAX backend. Neither Matt nor myself (not
being a maintainer for VAX, but I care about this!) did do a lot.
Would be great to have another port maintainer and I'm especially
happy that you'd consider working on the VAX code in your sponsor
project's time.
Thanks,
Jan-Benedict
--
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2021-10-21 8:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 14:39 Maciej W. Rozycki
2021-10-21 8:12 ` Jan-Benedict Glaw [this message]
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=20211021081211.olbykryeu4umpsrh@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=gcc@gcc.gnu.org \
--cc=macro@embecosm.com \
--cc=macro@orcam.me.uk \
--cc=matt@3am-software.com \
--cc=matt@netbsd.org \
/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).