From: "Marc Nieper-Wißkirchen" <marc.nieper+gnu@gmail.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: "Marc Nieper-Wißkirchen" <marc.nieper+gnu@gmail.com>,
"Marc Nieper-Wißkirchen via Jit" <jit@gcc.gnu.org>
Subject: Re: C++ API
Date: Mon, 24 Jan 2022 14:36:35 +0100 [thread overview]
Message-ID: <CAEYrNrSMpGEGXMjeyvtLMROStEV7OL017W8nSUcZ3e61NCi5Bg@mail.gmail.com> (raw)
In-Reply-To: <3783a5b520fe4dfdefb002638cc0ef0dd862a2a2.camel@redhat.com>
Am Sa., 22. Jan. 2022 um 16:40 Uhr schrieb David Malcolm <
dmalcolm@redhat.com>:
> On Sat, 2022-01-22 at 09:36 +0100, Marc Nieper-Wißkirchen via Jit
> wrote:
> > I just skimmed the documentation but it seems that the C++ API
> > exported by libgccjit++.h is not complete with respect to the later
> > additions to libgccjit. Is it planned to have it completed before GCC
> > 12 is released so that it is on par with the native C API?
>
> I created the C++ API for a specific project I was working on [1], but
> I haven't touched that project in years, and I'm not using the C++ API
> myself.
>
> I don't know of anyone else using the C++ API, and I'm not surprised if
> we've accidentally not kept it up to date with the new features.
>
I am about to use it and may have more feedback once I have done some
serious stuff with it.
> Is anyone out there using the C++ API? My recollection is that it
> saves a lot of typing compared to the plain C API - if you're already
> using C++ (which might be a step too far for many projects).
>
It's certainly useful.
> If anyone would like to fix the gaps, that would be great.
>
The additions of ABI tags 7, 16, and 17 seem to be missing.
prev parent reply other threads:[~2022-01-24 13:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 8:36 Marc Nieper-Wißkirchen
2022-01-22 15:40 ` David Malcolm
2022-01-24 13:36 ` Marc Nieper-Wißkirchen [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=CAEYrNrSMpGEGXMjeyvtLMROStEV7OL017W8nSUcZ3e61NCi5Bg@mail.gmail.com \
--to=marc.nieper+gnu@gmail.com \
--cc=dmalcolm@redhat.com \
--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).