From: akrl <akrl@sdf.org>
To: "Marc Nieper-Wißkirchen" <marc@nieper-wisskirchen.de>
Cc: dmalcolm@redhat.com, basile@starynkevitch.net, jit@gcc.gnu.org
Subject: Re: about header file parsing
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <xjf36pw9vs6.fsf@sdf.org> (raw)
In-Reply-To: <CAEYrNrTE-6VE=5nj0BZV=a-ekQnzK7Yv0n9bBVVCWHNbCLkDFA@mail.gmail.com> (message from Marc =?utf-8?Q?Nieper-Wi=C3=9Fkirchen?= on Sat, 12 Jan 2019 15:26:46 +0100)
Marc Nieper-Wißkirchen <marc@nieper-wisskirchen.de> writes:
> Am Do., 10. Jan. 2019 um 22:18 Uhr schrieb akrl <akrl@sdf.org>:
>
> [...]
>
>> Okay then lets go for gcc_jit_context_add_driver_option then.
>>
>> >
>> >> If we agree on an interface I propose my self to do the patch in
>> >> order
>> >> to have the occasion to setup the whole process.
>
> Thanks a lot, Andrea.
>
> I am wondering whether you could also make the procedures
> playback::context::invoke_embedded_driver and
> playback::context::invoke_external_driver available to client code of
> libgccjit. (If libgccjit is used as an AOT compiler, the user code may
> wish to invoke the driver independently. If the two procedures above
> are somehow exposed to user code, it doesn't have to duplicate the
> invocation code for an external driver and will be enabled to use the
> embedded driver as well.
>
> -- Marc
>
> [...]
>
Hi Marc,
there's no technical problem into including these into the patch.
But unless we have some special reason for that (like minimizing
LIBGCCJIT_ABI changes) I would rather prefer to have this changes as a
following patch.
But I guess is good to have Dave's opinion on all of these points.
Bests
Andrea
--
akrl@sdf.org
next prev parent reply other threads:[~2019-01-13 19:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 akrl
2019-01-01 0:00 ` Basile Starynkevitch
2019-01-01 0:00 ` Marc Nieper-Wißkirchen
2019-01-01 0:00 ` Marc Nieper-Wißkirchen
2019-01-01 0:00 ` Marc Nieper-Wißkirchen
2019-01-01 0:00 ` David Malcolm
2019-01-01 0:00 ` Marc Nieper-Wißkirchen
2019-01-01 0:00 ` David Malcolm
2019-01-01 0:00 ` akrl
2019-01-01 0:00 ` David Malcolm
2019-01-01 0:00 ` akrl
2019-01-01 0:00 ` Marc Nieper-Wißkirchen
2019-01-01 0:00 ` akrl [this message]
2019-01-01 0:00 ` Marc Nieper-Wißkirchen
2019-01-01 0:00 ` akrl
2019-01-01 0:00 ` Marc Nieper-Wißkirchen
2019-01-01 0:00 ` akrl
2019-01-01 0:00 ` David Malcolm
2019-01-01 0:00 ` akrl
2019-01-01 0:00 ` Basile Starynkevitch
2019-01-01 0:00 ` David Malcolm
2019-01-01 0:00 ` akrl
2019-01-01 0:00 ` Basile Starynkevitch
2019-01-01 0:00 ` David Malcolm
2019-01-01 0:00 ` Marc Nieper-Wißkirchen
2019-01-01 0:00 ` akrl
2019-01-01 0:00 ` Marc Nieper-Wißkirchen
2019-01-01 0:00 ` Basile Starynkevitch
2019-01-01 0:00 ` David Malcolm
2019-01-01 0:00 ` akrl
2019-01-01 0:00 ` David Malcolm
[not found] <df8944b7-1fbe-b56f-cc48-ab926d0cb5ad@starynkevitch.net>
2019-01-01 0:00 ` Basile Starynkevitch
2019-01-01 0:00 ` Marc Nieper-Wißkirchen
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=xjf36pw9vs6.fsf@sdf.org \
--to=akrl@sdf.org \
--cc=basile@starynkevitch.net \
--cc=dmalcolm@redhat.com \
--cc=jit@gcc.gnu.org \
--cc=marc@nieper-wisskirchen.de \
/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).