From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Suppressing native compilation (short and long term) Date: Wed, 28 Sep 2022 20:04:47 +0300 Message-ID: <834jwrig5s.fsf@gnu.org> References: <87ill8paw7.fsf@trouble.defaultvalue.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4255"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rlb@defaultvalue.org, emacs-devel@gnu.org To: Andrea Corallo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Sep 28 19:29:47 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1odasU-0000vA-TG for ged-emacs-devel@m.gmane-mx.org; Wed, 28 Sep 2022 19:29:47 +0200 Original-Received: from localhost ([::1]:44972 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1odasT-0006iH-Qj for ged-emacs-devel@m.gmane-mx.org; Wed, 28 Sep 2022 13:29:45 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59630) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1odaUY-0006q7-U7 for emacs-devel@gnu.org; Wed, 28 Sep 2022 13:05:10 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:33276) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1odaUX-0004jh-0v; Wed, 28 Sep 2022 13:05:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=N+xKoQEB1VBX+UqEXzPU9BmVOBgZlCnCFeQnJ6PtAfo=; b=JxLu1mCDZfyB VOWZAvEXBPld02D1aJbqmdhfvH5IrK6QEmC8bVrBA2nt6Aewc/0h9xmwodiYTn5Vnqbzq+stsckyv P/r4pTK5vZM98lzGohVIXm/m0ZD1uqK6FIBzm4jYCpkqSLU7hNU7cVfEO5VVBCQHbZjAQVVgzLKdA +RLSqCmd9u80mVlR9qMMQCQj7sEsdLpyRvj52CsDNnnO10E0kQRmMT4BPlcxE7m8y8i1BTdMpRfkN VEh8KmBvjiqc/AbATP/a5nmDM8WmSuVNMie3ahuRViArV6rsbfDYS1OrsHxKbiLBPTiDcI9O/wV9b ZG7deJ6srtaO0+vsw7mcZw==; Original-Received: from [87.69.77.57] (port=1624 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1odaUR-0002Ns-Or; Wed, 28 Sep 2022 13:05:00 -0400 In-Reply-To: (message from Andrea Corallo on Wed, 28 Sep 2022 12:52:59 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:296408 Archived-At: > From: Andrea Corallo > Cc: emacs-devel@gnu.org > Date: Wed, 28 Sep 2022 12:52:59 +0000 > > This is what `native-comp-deferred-compilation' does. Well except for > trampolines but this is extremly light as cpu/energy cost. I think if we want to allow people to turn off async compilation, we should provide a way to force native-comp-available-p to return nil. When that function returns nil, Emacs already does react correctly (or at least it's supposed to). But I still would like to understand what kind of use cases are we talking about here, because without that it's impossible to decide whether a given measure will provide a reasonable solution in the long run.