From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo Newsgroups: gmane.emacs.devel Subject: Re: Suppressing native compilation (short and long term) Date: Wed, 05 Oct 2022 13:47:10 +0000 Message-ID: References: <87bkqxf1ij.fsf@tethera.net> <83sfk6ahty.fsf@gnu.org> <8735c6b0wo.fsf@gnus.org> <87y1ty9lha.fsf@gnus.org> <87lepym6ok.fsf@trouble.defaultvalue.org> <877d1i9h7k.fsf@gnus.org> <83edvqyr3q.fsf@gnu.org> <874jwl8e4p.fsf@gnus.org> <87ill16t3a.fsf@gnus.org> <87edvp6nnf.fsf@gnus.org> <87a66d6lsw.fsf@gnus.org> <875yh16k59.fsf@gnus.org> <871qrp6itb.fsf@gnus.org> <871qrm5s5h.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23958"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Stefan Monnier , Eli Zaretskii , rlb@defaultvalue.org, david@tethera.net, emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Oct 05 16:02:06 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 1og4yM-00062a-Dv for ged-emacs-devel@m.gmane-mx.org; Wed, 05 Oct 2022 16:02:06 +0200 Original-Received: from localhost ([::1]:47066 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1og4yL-0004gl-FD for ged-emacs-devel@m.gmane-mx.org; Wed, 05 Oct 2022 10:02:05 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50476) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1og4k1-0000q9-Qj for emacs-devel@gnu.org; Wed, 05 Oct 2022 09:47:20 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:50760) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1og4jz-0008Vh-S5; Wed, 05 Oct 2022 09:47:17 -0400 Original-Received: from ma.sdf.org (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 295DlANi002935 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Wed, 5 Oct 2022 13:47:10 GMT In-Reply-To: <871qrm5s5h.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 05 Oct 2022 15:14:34 +0200") Received-SPF: pass client-ip=205.166.94.24; envelope-from=akrl@sdf.org; helo=mx.sdf.org X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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:296967 Archived-At: Lars Ingebrigtsen writes: > Andrea Corallo writes: > >> Again `inhibit-automatic-native-compilation' does not disable automatic >> trampoline native compilation :/ >> >> BTW I think most of people refers to what was controlled by >> `native-comp-deferred-compilation' as a jitter mechanism, so I think a >> better name would have been `inhibit-native-jit-compilation'. I wish >> this change was not rushed. > > I don't think `inhibit-native-jit-compilation' conveys anything more to > the user than `inhibit-automatic-native-compilation'? That's your opinion and I respect it. Still `inhibit-automatic-native-compilation' does *not* disable automatic native compilation but only a mechanism contributing to it, so it's IMO a bad naming decision. > Andrea Corallo writes: > >> We can discuss code also on branches, there's no need to install changes >> on master to discuss them. >> >> I'm back now after a long weekend and your proposal of introduciung >> `inhibit-native-compilation' is form 2 days and 1 hour ago. Sorry but I >> don't want to feel that changes can be rushed into Emacs code and in >> order to partecipate to the discussion people can't have some time off. > > Development takes place on the "master" branch -- code appearing there > does not curtail further discussion. I have not said that once code is in master discussion is forbidden. I said that to discuss a change there's *no* requirement to install it in master, especially before sufficient discussion is done on the list for these tricky interfaces. My 2cts are that these mechanisms and changes should be very well thought and participated before being modified. As maintainer of comp.c and related I ask to have this changeset reverted and then we restart thinking again what's the best change (if any) needed here. Thanks Andrea