From: David Malcolm <dmalcolm@redhat.com>
To: "Marc Nieper-Wißkirchen" <marc.nieper+gnu@gmail.com>,
"Marc Nieper-Wißkirchen via Jit" <jit@gcc.gnu.org>
Subject: Re: gccjit::context::get_first_error documented but not implemented
Date: Mon, 31 Jan 2022 09:50:43 -0500 [thread overview]
Message-ID: <35bd6c7e52fc2308dcf32005d0586bc7e38a2d6d.camel@redhat.com> (raw)
In-Reply-To: <CAEYrNrTjxtvBhOdeaRGhTPE=Lcanrs9Te5PaYvoYMM39B6s3cg@mail.gmail.com>
On Sun, 2022-01-30 at 16:08 +0100, Marc Nieper-Wißkirchen via Jit
wrote:
> The method
>
> gccjit::context
> <
> https://gcc.gnu.org/onlinedocs/jit/cp/topics/contexts.html#_CPPv3N6gccjit7contextE
> >
> ::get_first_error
>
> is documented ([1]), but a search in libgccjit++.h reveals no
> implementation.
...and there's also get_last_error (which I think is neither
implemented, or documented).
Dave
>
> --
>
> [1]
> https://gcc.gnu.org/onlinedocs/jit/cp/topics/contexts.html#_CPPv3N6gccjit7context15get_first_errorEPN6gccjit7contextE
>
prev parent reply other threads:[~2022-01-31 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 15:08 Marc Nieper-Wißkirchen
2022-01-31 14:50 ` 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=35bd6c7e52fc2308dcf32005d0586bc7e38a2d6d.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=jit@gcc.gnu.org \
--cc=marc.nieper+gnu@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).