From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#33014: 26.1.50; 27.0.50; Fatal error after re-evaluating a thread's function Date: Wed, 17 Oct 2018 19:21:01 +0300 Message-ID: <8336t4sfwy.fsf@gnu.org> References: <87d0sh9hje.fsf@runbox.com> <83murjwplq.fsf@gnu.org> <87zhvjc4r3.fsf@runbox.com> <83y3b2uzyt.fsf@gnu.org> <87va65daw9.fsf@runbox.com> <8336t9vi3h.fsf@gnu.org> <87ftx89uqs.fsf@igel.home> <837eijtfw1.fsf@gnu.org> <878t2xd90z.fsf@runbox.com> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1539793218 3702 195.159.176.226 (17 Oct 2018 16:20:18 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 17 Oct 2018 16:20:18 +0000 (UTC) Cc: 33014@debbugs.gnu.org, schwab@linux-m68k.org To: Gemini Lasswell Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Oct 17 18:20:13 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gCoYN-0000nF-AB for geb-bug-gnu-emacs@m.gmane.org; Wed, 17 Oct 2018 18:20:11 +0200 Original-Received: from localhost ([::1]:38046 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gCoaT-0007U6-FT for geb-bug-gnu-emacs@m.gmane.org; Wed, 17 Oct 2018 12:22:21 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37447) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gCoaM-0007Tm-At for bug-gnu-emacs@gnu.org; Wed, 17 Oct 2018 12:22:15 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gCoaF-0004zA-Q9 for bug-gnu-emacs@gnu.org; Wed, 17 Oct 2018 12:22:11 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:51267) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gCoaA-0004m2-No for bug-gnu-emacs@gnu.org; Wed, 17 Oct 2018 12:22:04 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gCoaA-0006HC-Fc for bug-gnu-emacs@gnu.org; Wed, 17 Oct 2018 12:22:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 17 Oct 2018 16:22:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 33014 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 33014-submit@debbugs.gnu.org id=B33014.153979327924067 (code B ref 33014); Wed, 17 Oct 2018 16:22:02 +0000 Original-Received: (at 33014) by debbugs.gnu.org; 17 Oct 2018 16:21:19 +0000 Original-Received: from localhost ([127.0.0.1]:55525 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gCoZT-0006G7-2h for submit@debbugs.gnu.org; Wed, 17 Oct 2018 12:21:19 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:55874) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gCoZR-0006Fr-BN for 33014@debbugs.gnu.org; Wed, 17 Oct 2018 12:21:17 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gCoZI-0003G2-Uu for 33014@debbugs.gnu.org; Wed, 17 Oct 2018 12:21:12 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:40960) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gCoZI-0003Fe-PW; Wed, 17 Oct 2018 12:21:08 -0400 Original-Received: from [176.228.60.248] (port=1944 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1gCoZH-0000Ii-Sk; Wed, 17 Oct 2018 12:21:08 -0400 In-reply-to: <878t2xd90z.fsf@runbox.com> (message from Gemini Lasswell on Tue, 16 Oct 2018 11:46:36 -0700) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 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.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:151347 Archived-At: > From: Gemini Lasswell > Cc: Andreas Schwab , 33014@debbugs.gnu.org > Date: Tue, 16 Oct 2018 11:46:36 -0700 > > My knowledge of what gcc does and how the code it generates works is > superficial, but I don't see why an optimizer would find it necessary to > save the following values: > > - The value of 'fun' in Ffuncall after it is used as an argument for > funcall_lambda. > > - The value of 'fun' in funcall_lambda after it is used to calculate > the arguments to exec_byte_code. > > - The value of 'vector' in exec_byte_code after the calculation of > vectorp. After thinking about this a bit, I don't really agree with the last one: the compiler could indeed stop tracking 'vector', but not XVECTOR (vector)->contents, and we are interested in the latter. One other thought is that, if worse comes to worst, we may consider disallowing redefinition of a function that is currently being executed (in another thread). However, I'm still not convinced we are there. Can we establish which element(s) of the bytecode vector are GC'ed in this scenario?