From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yb1-xb32.google.com (mail-yb1-xb32.google.com [IPv6:2607:f8b0:4864:20::b32]) by sourceware.org (Postfix) with ESMTPS id 727A03858D39 for ; Mon, 24 Jan 2022 13:36:47 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 727A03858D39 Received: by mail-yb1-xb32.google.com with SMTP id c6so51371051ybk.3 for ; Mon, 24 Jan 2022 05:36:47 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=8tU+J8Jg4lccUldBJtAMHSFPbr7a7P6jd/YeN4pES7I=; b=qGaQCmLpuisvRcKOahJr9zikQcSmfGWyV7sfGWvsluc6MSqen5KBtckEsseV2fHrp3 qdujTdZMxcF4D+xTfI0cr4OKzzMJyDgSGoasx74fLzXo1my+DdCVuIDmlo8NAmBQq0/5 27teXr5SGCWImDjM2967IIU7A0gJ0+MjEmKfP5fYUojRaVMAKYRaM0x5NOnMvyeWgou2 CvZIOuuvcG1rJbU6qNLdRRLQqzGgWJTtmo/q7vqUc8cnDnSq0Cd7kqlu4DRgOpnKtIRx uVMCfuE2av+NLHFyYrtMlN3NrAFZxCKzqVzZPkuJ4cUZJBSrbsissd05efPVwQh4gKf6 gaWw== X-Gm-Message-State: AOAM530MD0S77QPFOlHEqj6bsxY7kkikrf/EIYFNt9BEQIT9WqKdKvFE L6yjFHV9Q+EGMqvj93QhRU2yIj2WMjm30+jHrZA= X-Google-Smtp-Source: ABdhPJwKdAVQnhGVQPrP9wbyWtUv8YAc945zJ/NrMaLcdP8+qOJQrIvEqlmBWzaacdj8BYKYkDv4jmAwCEZiLSoXAEc= X-Received: by 2002:a05:6902:906:: with SMTP id bu6mr6821940ybb.554.1643031406897; Mon, 24 Jan 2022 05:36:46 -0800 (PST) MIME-Version: 1.0 References: <3783a5b520fe4dfdefb002638cc0ef0dd862a2a2.camel@redhat.com> In-Reply-To: <3783a5b520fe4dfdefb002638cc0ef0dd862a2a2.camel@redhat.com> From: =?UTF-8?Q?Marc_Nieper=2DWi=C3=9Fkirchen?= Date: Mon, 24 Jan 2022 14:36:35 +0100 Message-ID: Subject: Re: C++ API To: David Malcolm Cc: =?UTF-8?Q?Marc_Nieper=2DWi=C3=9Fkirchen?= , =?UTF-8?Q?Marc_Nieper=2DWi=C3=9Fkirchen_via_Jit?= X-Spam-Status: No, score=0.0 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: jit@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Jit mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2022 13:36:48 -0000 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=C3=9Fkirchen 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.