From: Andrea Corallo via "Emacs development discussions." <emacs-devel@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: arthur.miller@live.com, emacs-devel@gnu.org
Subject: Re: Native compiler - passing command line options to C compiler
Date: Mon, 30 Aug 2021 14:28:18 +0000 [thread overview]
Message-ID: <xjfeeab2eil.fsf@ma.sdf.org> (raw)
In-Reply-To: <83v93njc3x.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 30 Aug 2021 16:28:18 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Andrea Corallo <akrl@sdf.org>
>> Cc: Arthur Miller <arthur.miller@live.com>, emacs-devel@gnu.org
>> Date: Mon, 30 Aug 2021 12:59:45 +0000
>>
>> I think this "defined (WINDOWSNT)" should be there so that compiling on
>> Windows the check over "gcc_jit_context_add_command_line_option" it is
>> always compiled even in case the libgccjit.h provided at compile time
>> does not define
>> 'LIBGCCJIT_HAVE_gcc_jit_context_add_command_line_option'.
>>
>> A newer version of the shared library including the entry point might be
>> provided later on and will be used at runtime.
>
> You cannot use a libgccjit.dll of a version for which Emacs was not
> compiled, unless it is binary-compatible. If Emacs was linked against
> libgccjit.dll that didn't support
> gcc_jit_context_add_command_line_option, then it would not work to
> install a newer version of the DLL that does.
Okay, I thought on Windows worked differently and we could handle the
case of a symbol not available at compile time but at runtime. In the
light of this we can probably perform some more clean-up.
Thanks
Andrea
next prev parent reply other threads:[~2021-08-30 14:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AM9PR09MB49778CFA83AA6697D09ED01B96CA9@AM9PR09MB4977.eurprd09.prod.outlook.com>
2021-08-30 9:36 ` Native compiler - passing command line options to C compiler Andrea Corallo via Emacs development discussions.
2021-08-30 13:56 ` Arthur Miller
2021-08-30 14:05 ` Andrea Corallo via Emacs development discussions.
2021-08-30 11:42 ` Eli Zaretskii
2021-08-30 12:59 ` Andrea Corallo via Emacs development discussions.
2021-08-30 13:28 ` Eli Zaretskii
2021-08-30 14:28 ` Andrea Corallo via Emacs development discussions. [this message]
2021-08-30 15:00 ` Arthur Miller
2021-08-30 15:38 ` Andrea Corallo via Emacs development discussions.
2021-08-31 5:36 ` Arthur Miller
2021-08-31 8:06 ` Andrea Corallo via Emacs development discussions.
2021-08-31 13:01 ` Eli Zaretskii
2021-08-31 22:53 ` Arthur Miller
2021-09-01 11:45 ` Eli Zaretskii
2021-09-01 14:23 ` Arthur Miller
2021-09-01 16:45 ` Eli Zaretskii
2021-09-01 21:06 ` Arthur Miller
2021-08-30 16:01 ` Eli Zaretskii
2021-08-30 15:50 ` Eli Zaretskii
2021-08-30 14:01 ` Arthur Miller
2021-08-30 14:03 ` Eli Zaretskii
2021-09-01 14:58 ` Alex Bennée
2021-09-01 15:10 ` Perry E. Metzger
2021-09-01 16:04 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xjfeeab2eil.fsf@ma.sdf.org \
--to=emacs-devel@gnu.org \
--cc=akrl@sdf.org \
--cc=arthur.miller@live.com \
--cc=eliz@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).