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.bugs Subject: bug#58509: 29.0.50; Synchronous nativecomp Date: Sun, 23 Oct 2022 12:10:20 +0000 Message-ID: References: <87a65yd715.fsf@gnus.org> <87a65x786i.fsf@gnus.org> <871qr82lu6.fsf@gnus.org> <87v8oielxp.fsf@gnus.org> <878rleek7y.fsf@gnus.org> <834jw236v8.fsf@gnu.org> <87edv6ckof.fsf@gnus.org> <83fsfl1c3r.fsf@gnu.org> <83mt9tynr9.fsf@gnu.org> <838rlbzl0a.fsf@gnu.org> <83tu3zxaeu.fsf@gnu.org> <83pmemyl4o.fsf@gnu.org> <83lep6sr2p.fsf@gnu.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="21078"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: larsi@gnus.org, 58509@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Oct 24 06:45:00 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1ompKd-0005GI-Ez for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 24 Oct 2022 06:44:59 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ommNS-0000z2-L3 for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 23 Oct 2022 21:35:42 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1omZok-0006NF-D1 for bug-gnu-emacs@gnu.org; Sun, 23 Oct 2022 08:11:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1omZok-0007dz-5t for bug-gnu-emacs@gnu.org; Sun, 23 Oct 2022 08:11:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1omZoj-0005QM-T2 for bug-gnu-emacs@gnu.org; Sun, 23 Oct 2022 08:11:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Andrea Corallo Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 23 Oct 2022 12:11:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 58509 X-GNU-PR-Package: emacs Original-Received: via spool by 58509-submit@debbugs.gnu.org id=B58509.166652704320825 (code B ref 58509); Sun, 23 Oct 2022 12:11:01 +0000 Original-Received: (at 58509) by debbugs.gnu.org; 23 Oct 2022 12:10:43 +0000 Original-Received: from localhost ([127.0.0.1]:43799 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1omZoN-0005Pk-8K for submit@debbugs.gnu.org; Sun, 23 Oct 2022 08:10:43 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:55344) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1omZo6-0005PN-Fz for 58509@debbugs.gnu.org; Sun, 23 Oct 2022 08:10:37 -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 29NCAKKp005331 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Sun, 23 Oct 2022 12:10:21 GMT In-Reply-To: <83lep6sr2p.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 23 Oct 2022 14:43:42 +0300") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:246077 Archived-At: Eli Zaretskii writes: >> From: Andrea Corallo >> Cc: larsi@gnus.org, 58509@debbugs.gnu.org >> Date: Sun, 23 Oct 2022 10:51:14 +0000 >> >> Eli Zaretskii writes: >> >> >> Okay so IIUC your suggestion would be to: when we identify '--batch' we >> >> search for a signature in the commandline to identify the trampoline >> >> compilation and set in case `comp-no-spawn'? >> > >> > Yes. And if that works, my next question is: can we then remove the >> > new -no-comp-spawn command-line option, or do we need it for some >> > other cases? >> >> If it works I think it should be equivalent at that point. But at the >> moment is not so trivial to identify this condition as we have no clear >> marker of it. >> >> The current invocation for compilations is just like: >> >> emacs --batch -l sometmpfile.el >> >> I don't know if we have some other option for adding a marker other than >> the most obvious (the dedicated flag). > > At some point during compilation, we surely know that we are compiling > a trampoline, right? So I thought to avoid forking at that point, so > that we don't need yet another command-line option for internal > purposes. That's correct, but I believe the issue is that when we realize we are compiling a trampoline it's too late, and we might have been decided already a new trampoline needs to be compiled and installed. The parsing of the command line args happens way earlier and that's why this technique works at solving this issue. Andrea