unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <akrl@sdf.org>
To: Tor Kringeland <tor.kringeland@ntnu.no>
Cc: Stephen Leake <stephen_leake@stephe-leake.org>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: disable automatic native-compilation?
Date: Mon, 11 Jul 2022 12:54:07 +0000	[thread overview]
Message-ID: <xjfleszq07k.fsf@ma.sdf.org> (raw)
In-Reply-To: <m2mtdhx69l.fsf@ntnu.no> (Tor Kringeland's message of "Sat, 9 Jul 2022 22:36:55 +0000")

Tor Kringeland <tor.kringeland@ntnu.no> writes:

> Stephen Leake <stephen_leake@stephe-leake.org> writes:
>
>> - There should be a simple way to completely disable native compilation;
>> Emacs should never do anything that I can't control. If setting
>> native-comp-deferred-compilation nil is the right way to do this, it
>> should be documented in the native compilation section of the elisp
>> manual.
>
> Doesn't setting
>
>   (setq native-comp-speed -1)
>
> disable native compilation?

Not "completely".  `native-comp-speed' works at function per function
level.  A function copiled with native-comp-speed -1 will still be
enclosed in the produced .eln file but in bytecode form.  Indeed setting
it globally will have as result the production of the same .eln files
but those will include the bytecode definition of the compiled
functions.

BR

  Andrea



  parent reply	other threads:[~2022-07-11 12:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-09 16:49 disable automatic native-compilation? Stephen Leake
2022-07-09 17:23 ` Eli Zaretskii
2022-07-10 15:10   ` Lynn Winebarger
2022-07-10 15:39     ` Eli Zaretskii
2022-07-10 18:32       ` Lynn Winebarger
2022-07-10 21:54         ` Ken Brown
2022-07-11  1:52           ` Ken Brown
2022-07-11  2:39             ` Lynn Winebarger
2022-07-11 13:37               ` Ken Brown
2022-07-11 13:56                 ` Eli Zaretskii
2022-07-11 17:19                   ` Ken Brown
2022-07-09 22:36 ` Tor Kringeland
2022-07-10  8:58   ` Philip Kaludercic
2022-07-11 12:54   ` Andrea Corallo [this message]
2022-07-12 11:04     ` Tor Kringeland
2022-07-12 11:27       ` Tor Kringeland
2022-07-12 13:29         ` Eli Zaretskii
2022-08-06 15:32 ` Lynn Winebarger

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=xjfleszq07k.fsf@ma.sdf.org \
    --to=akrl@sdf.org \
    --cc=emacs-devel@gnu.org \
    --cc=stephen_leake@stephe-leake.org \
    --cc=tor.kringeland@ntnu.no \
    /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).