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: MPS: native comp Date: Tue, 30 Apr 2024 03:36:13 -0400 Message-ID: References: <86le4wsj14.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24389"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Eli Zaretskii , emacs-devel@gnu.org To: Gerd =?utf-8?Q?M=C3=B6llmann?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Apr 30 09:37:35 2024 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 1s1i3T-00067u-N2 for ged-emacs-devel@m.gmane-mx.org; Tue, 30 Apr 2024 09:37:35 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1s1i2c-0000TZ-Tw; Tue, 30 Apr 2024 03:36: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 1s1i2P-0000SQ-D6 for emacs-devel@gnu.org; Tue, 30 Apr 2024 03:36:33 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s1i2M-00042t-1T; Tue, 30 Apr 2024 03:36:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:References:In-Reply-To:Subject:To: From; bh=LSg9U2DUy4TDWVb9Qkc0JpUA4UA88j/ADmVVulQyslE=; b=l04tXo8vFGAE+RAyXR0L Jb213KpkkmJBEf97M5k9B/kjutt+u3pLAxckWmkrY/kljewIkWigpTIdO6NU2hSfFD6s+kTp5bs2G H/JzIWwjIs5sD+EqkY1wpaY61tKwORctTN5C4DBNPUxCV50cWbCVxMMVW142BLsKltY4/f7NJlYNa 6K8iIwWqbek7aYle3tsoRAcGktOOLc/M2AS+lSlCXrgNiNvjPX4mK1apv/YUqctGDFFCAqCknSfb1 N0pSn0Gjo/qWlo/xQiVjtmn8sy18TXUjo6Z5icCbeUXPlZIYmGZ3vAeiWn4oapvRE00FEQeNU10Ow 3a9QA7EZglneRA==; Original-Received: from acorallo by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1s1i29-0003NB-TZ; Tue, 30 Apr 2024 03:36:23 -0400 In-Reply-To: ("Gerd =?utf-8?Q?M=C3=B6llman?= =?utf-8?Q?n=22's?= message of "Tue, 30 Apr 2024 06:39:54 +0200") 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:318401 Archived-At: Gerd M=C3=B6llmann writes: > Gerd M=C3=B6llmann writes: > >> Progress. Same scenario as before and we come to pdumping, but it >> complains >> >> ./temacs --batch -l loadup --temacs=3Dpbootstrap \ >> --bin-dest --eln-dest >> ... >> Loading emacs-lisp/macroexp (native compiled elisp)... >> .. >> Dumping under the name bootstrap-emacs.pdmp >> Dumping fingerprint: 4ff41caeb772618cf9be4dd61ae8a1cf909c29b0ff417318e= c6039950eaf53fc >> >> Error: error ("trying to dump non fixed-up eln file") >> > > Actually, and strangely, I get a different error when running under > LLDB. > > Loading /Users/gerd/emacs/savannah/igc/lisp/emacs-lisp/cl-generic.el (s= ource)... > Loading /Users/gerd/emacs/savannah/igc/lisp/simple.el (source)... > > Error: error ("Eager macro-expansion failure: (setting-constant byte-co= mpile-form-stack)") > signal(error ("Eager macro-expansion failure: (setting-constant byte-= compile-form-stack)")) > > In a way that makes more sense because we saw that "Eager..." string > before. byte-compile-form-stack is a var defined in macroexp. > > Does someone know what "eager" macro expansion means? In what way is it > eager? Or different from non-eager (lazy?) macro expansion? But why > would ME be lazy? Questions about questions... AFAIU it's when we do macro expansions before execution, read every time we byte/native compile. The error typically implies something goes wrong in the macro expander (which is one of the first native compiled pieces of code leveraged during a native bootstrap). IOH native compiled code is probably still not functional for some reason. A simpler testcase should help narrowing down the issue excluding all the bootstrap complexity. Andrea