* C++ API
@ 2022-01-22 8:36 Marc Nieper-Wißkirchen
2022-01-22 15:40 ` David Malcolm
0 siblings, 1 reply; 3+ messages in thread
From: Marc Nieper-Wißkirchen @ 2022-01-22 8:36 UTC (permalink / raw)
To: Marc Nieper-Wißkirchen via Jit
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?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: C++ API
2022-01-22 8:36 C++ API Marc Nieper-Wißkirchen
@ 2022-01-22 15:40 ` David Malcolm
2022-01-24 13:36 ` Marc Nieper-Wißkirchen
0 siblings, 1 reply; 3+ messages in thread
From: David Malcolm @ 2022-01-22 15:40 UTC (permalink / raw)
To: Marc Nieper-Wißkirchen, Marc Nieper-Wißkirchen via Jit
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.
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).
If anyone would like to fix the gaps, that would be great.
Dave
[1] experimental port of GNU Octave's JIT compiler to libgccjit;
https://savannah.gnu.org/patch/index.php?8395 )
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: C++ API
2022-01-22 15:40 ` David Malcolm
@ 2022-01-24 13:36 ` Marc Nieper-Wißkirchen
0 siblings, 0 replies; 3+ messages in thread
From: Marc Nieper-Wißkirchen @ 2022-01-24 13:36 UTC (permalink / raw)
To: David Malcolm
Cc: Marc Nieper-Wißkirchen, Marc Nieper-Wißkirchen via Jit
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-01-24 13:36 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-22 8:36 C++ API Marc Nieper-Wißkirchen
2022-01-22 15:40 ` David Malcolm
2022-01-24 13:36 ` Marc Nieper-Wißkirchen
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).