[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] [WIP] Port feature/native-comp to Windows.

From: Andrea Corallo
Subject: Re: [PATCH] [WIP] Port feature/native-comp to Windows.
Date: Sun, 10 May 2020 11:14:11 -0700
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)

Eli Zaretskii <address@hidden> writes:

>> From: Andrea Corallo <address@hidden>
>> Cc: Eli Zaretskii <address@hidden>, address@hidden
>> Date: Sun, 10 May 2020 10:13:08 -0700
>> For the rest I do not have Windows knowledge so to form an opinion I'd
>> need to understand a little more how it works.
> Can you describe how we find the GCC auxiliary programs and support
> libraries needed for native compilation on GNU/Linux?

libgccjit when has produced the .s file has to invoke the "driver".
This is in GCC jargon the usual gcc executable that his the program that
is responsible for calling cc1 as and ld.

libgccjit can invoke the driver in two ways, one is using the embedded
one (default) or it can search for an external driver (the system gcc
executable).  AFAIU when the driver takes over the conventional logic to
identify support library is used by the linker.

Using gcc_jit_context_add_driver_option you can pass parameters to the
driver that will forward them to the linker.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]