|
From: | Michael Heerdegen |
Subject: | Re: Enabling native compilation by default when libgccjit is present |
Date: | Thu, 09 Dec 2021 06:27:15 +0100 |
User-agent: | Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
Stefan Monnier <monnier@iro.umontreal.ca> writes: > Such warnings usually imply real errors (the resulting file will not > work properly because it contains code that "calls" a macro as if it > were a function (i.e. after have evaluated the arguments)). Usually yes, but not for my init file because it is always loaded when I compile it. And the same code also works interpreted. And because of all the dependencies of my init file I never came into the embarrassment to compile it "in a clean environment". So these issues are hard to detect (in this special case) and never had consequences - until now (where those real errors got real real errors). Michael.
[Prev in Thread] | Current Thread | [Next in Thread] |