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: Wed, 26 Oct 2022 06:40:06 +0000 Message-ID: References: <87a65yd715.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> <83fsfbnwor.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="36177"; 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 Wed Oct 26 08:42:04 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 1ona72-0009A2-H4 for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 26 Oct 2022 08:42:04 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ona6K-0007Wf-HP; Wed, 26 Oct 2022 02:41:20 -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 1ona63-0006Yv-54 for bug-gnu-emacs@gnu.org; Wed, 26 Oct 2022 02:41:11 -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 1ona62-0000XO-Tn for bug-gnu-emacs@gnu.org; Wed, 26 Oct 2022 02:41:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ona61-0002Zr-Ng for bug-gnu-emacs@gnu.org; Wed, 26 Oct 2022 02:41: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: Wed, 26 Oct 2022 06:41: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.16667664129836 (code B ref 58509); Wed, 26 Oct 2022 06:41:01 +0000 Original-Received: (at 58509) by debbugs.gnu.org; 26 Oct 2022 06:40:12 +0000 Original-Received: from localhost ([127.0.0.1]:53093 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ona5D-0002YZ-Nn for submit@debbugs.gnu.org; Wed, 26 Oct 2022 02:40:11 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:49932) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ona5B-0002YN-Tr for 58509@debbugs.gnu.org; Wed, 26 Oct 2022 02:40:10 -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 29Q6e6I6026665 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Wed, 26 Oct 2022 06:40:07 GMT In-Reply-To: <83fsfbnwor.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 26 Oct 2022 05:30:28 +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: , Original-Sender: "bug-gnu-emacs" Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:246197 Archived-At: Eli Zaretskii writes: >> From: Andrea Corallo >> Cc: larsi@gnus.org, 58509@debbugs.gnu.org >> Date: Tue, 25 Oct 2022 19:54:27 +0000 >> >> >>> 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 >> >> What do we want to do? Shall I push my patch that fixes the trampoline >> bomb with the use of -no-comp-spawn? > > Oh, I thought you already did? > > Yes, please install that. Done, into trunk as 5ad5b797f7. Thanks Andrea