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: The emacs-28 release branch has been created Date: Tue, 05 Oct 2021 14:43:57 +0300 Message-ID: <83tuhv4rya.fsf@gnu.org> References: <83lf3dgbl3.fsf@gnu.org> <6c7a9f1a-bf2d-4213-b954-2025eee1f282@cornell.edu> <838rzaa264.fsf@gnu.org> <2434455f-34f5-3e6b-b26f-db7b66cf8f3d@cornell.edu> <83ee9287ef.fsf@gnu.org> <83a6jq84wu.fsf@gnu.org> <10401c4a-1d0a-817c-942e-f08ab3130552@cornell.edu> <834k9y814j.fsf@gnu.org> <83tuhx7w54.fsf@gnu.org> <30b78a17-2b95-5d0c-fb46-10c37ee91638@cornell.edu> <96912815-d275-8b54-9ba8-cc4fd5b0fe91@cornell.edu> <83v92c6f4n.fsf@gnu.org> <83sfxg6ehc.fsf@gnu.org> <83r1d06dry.fsf@gnu.org> <83h7dw681k.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12582"; mail-complaints-to="usenet@ciao.gmane.io" Cc: kbrown@cornell.edu, emacs-devel@gnu.org To: Andrea Corallo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Oct 05 13:53:36 2021 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 1mXj0q-00034b-10 for ged-emacs-devel@m.gmane-mx.org; Tue, 05 Oct 2021 13:53:36 +0200 Original-Received: from localhost ([::1]:40592 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mXj0o-0007ag-Tv for ged-emacs-devel@m.gmane-mx.org; Tue, 05 Oct 2021 07:53:34 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38102) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mXirn-00070Y-5O for emacs-devel@gnu.org; Tue, 05 Oct 2021 07:44:15 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:33778) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mXirj-0004S1-Lv; Tue, 05 Oct 2021 07:44:11 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:2178 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 1mXirf-00017E-EG; Tue, 05 Oct 2021 07:44:11 -0400 In-Reply-To: (message from Andrea Corallo on Mon, 04 Oct 2021 19:38:43 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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:276320 Archived-At: > From: Andrea Corallo > Cc: kbrown@cornell.edu, emacs-devel@gnu.org > Date: Mon, 04 Oct 2021 19:38:43 +0000 > > - I reduced the reproducer searching manually by bissection in the file > for the function causing the ICE So the problem caused an ICE in libgccjit, is that right? Is that always so when the error message says Lisp error: (native-compiler-error ... ? Because the error message then said "(invalid-read-syntax...", which sounds like a message coming from Emacs, not from the compiler. Also, we probably want to avoid the ellipsis in batch invocations, because (unlike in interactive usage) they cannot be expanded. Is that something that comp.el controls, or is that a general "feature" of Emacs? > - I read carefully the stack trace of the compiler (after having posted > it here :/ ) and saw that the reader error was not on file being > compiled but on the file that we use to drive the native compilation > happening in the subprocess (the one generated by `comp-final'). How did you see that? The backtrace says: > akrl@xxx:~/emacs2/lisp$ ../src/emacs -batch --no-site-file --no-site-lisp --eval '(setq load-prefer-newer t)' -l comp -f byte-compile-refresh-preloaded --eva\ > l '(batch-native-compile t)' disp-table.el > Debugger entered--Lisp error: (native-compiler-error "disp-table.el" "Debugger entered--Lisp error: (end-of-file \"/tmp/e...") > signal(native-compiler-error ("disp-table.el" "Debugger entered--Lisp error: (end-of-file \"/tmp/e...")) > comp--native-compile("disp-table.el") > batch-native-compile(t) > command-line-1(("--eval" "(setq load-prefer-newer t)" "-l" "comp" "-f" "byte-compile-refresh-preloaded" "--eval" "(batch-native-compile t)" "disp-table.el")) > command-line() > normal-top-level() So it only says "end of file", and the file name is not spelled out. And btw, this backtrace is different from what I saw originally: that one didn't say "end of file". Why this one did? > - I looked into one of these files and I saw clearly in the limple dump > a constant vector that is truncated (not sure why maybe we have to > bind some other print-something var in comp final?). I'd like to understand why stuff gets truncated in that case. Thanks.