From: Nick Clifton <nickc@redhat.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: RFA: Another Rust demangler recursion limit
Date: Mon, 4 Jul 2022 11:08:06 +0100 [thread overview]
Message-ID: <72dd9830-35e0-17f1-e817-b1d3b60a511f@redhat.com> (raw)
In-Reply-To: <2f573379-e4c1-cf89-1644-df3067bc6f9a@gmail.com>
Hi Jeff,
> OK.
Thanks.
> And yes, I wish someone else was looking at this stuff. Rust isn't really on my radar right now...
I have been toying with the idea of putting myself forward as a maintainer
for the libiberty sources. I just wish that I had more free time...
Cheers
Nick
prev parent reply other threads:[~2022-07-04 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 15:12 Nick Clifton
2022-07-01 16:53 ` Jeff Law
2022-07-04 10:08 ` Nick Clifton [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=72dd9830-35e0-17f1-e817-b1d3b60a511f@redhat.com \
--to=nickc@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
/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).