From: David Malcolm <dmalcolm@redhat.com>
To: Andrea Corallo <akrl@sdf.org>, gcc@gcc.gnu.org
Cc: jit@gcc.gnu.org
Subject: Re: libgccjit maintenance status
Date: Wed, 01 Jan 2020 00:00:00 -0000 [thread overview]
Message-ID: <dcd76f9eb569c3dd4ea6d80b47bb8bbcc115af64.camel@redhat.com> (raw)
In-Reply-To: <xjftv32pp45.fsf@sdf.org>
On Thu, 2020-03-05 at 19:40 +0000, Andrea Corallo wrote:
> Hi all,
>
> I'd like to ask about the maintenance status of libgccjit.
I'm the maintainer. GCC 10 is currently in stage 4 so making changes
may require release-manager signoff.
> Personally (in my spare time) I'd like to contribute more to it but I
> feel the development is a little stuck and patches don't get
> reviewed[1].
Sorry about that. I know I lost some email at the end of last year,
and I've been very busy working on the static analyzer [2].
Please ping the list weekly if I'm not getting around to reviewing
patches.
> More widely speaking we have a feature branch under active
> development in emacs.git that relies on libgccjit therefore its
> maintenance status is a fundamental information to have.
>
> Alternatively what can I do to help speed up the review of these
> patches?
>
> Thanks and Regards
>
> Andrea
>
> [1] https://gcc.gnu.org/ml/jit/2020-q1/msg00002.html
> https://gcc.gnu.org/ml/jit/2020-q1/msg00001.html
I'll take a look at these today.
Sorry about the delay
Dave
[2] https://gcc.gnu.org/wiki/DavidMalcolm/StaticAnalyzer
prev parent reply other threads:[~2020-03-05 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 0:00 Andrea Corallo
2020-01-01 0:00 ` David Malcolm [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=dcd76f9eb569c3dd4ea6d80b47bb8bbcc115af64.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=akrl@sdf.org \
--cc=gcc@gcc.gnu.org \
--cc=jit@gcc.gnu.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).