[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 12:47:07 -0700
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)

Eli Zaretskii <address@hidden> writes:

>> From: Nicolas Bértolo <address@hidden>
>> Date: Sun, 10 May 2020 16:02:11 -0300
>> Cc: Andrea Corallo <address@hidden>, address@hidden
>> > This is known in advance.  We already have that knowledge in Emacs,
>> > see HAVE__SETJMP and HAVE_SIGSETJMP used in lisp.h.
>> > I don't yet understand why we need the _name_ of the setjmp function.
>> > How will this name be used?
>> I think it is a good idea to show how the information is used:
>> This is the function that generates a function call to `setjmp`.
> Thanks, I will think about this.  But up front, we can simply use the
> apriori knowledge about the way the setjmp macro is expanded in the
> version used for building Emacs.  We could build in some defenses
> against changes in that expansion, if that is a real danger, but
> that's not urgent.

I think one easy way to find in the configure the function name would be
trying the compilation of few test programs till we succeed with the one
that uses the right function name.  This way is a little hacky but way
simpler than parsing the expansion.



reply via email to

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