From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: Certain numbers of special forms cause changing behaviour on function calls in --batch Date: Sun, 10 Jul 2016 20:40:52 +0200 Message-ID: <578296B4.7040604@cs.ucla.edu> References: <8760stvwzp.fsf@web.de> <834m8cvu9p.fsf@gnu.org> <87h9cbpw61.fsf@web.de> <83wpl7v1sg.fsf@gnu.org> <87a8i2dfe3.fsf@web.de> <83poqyvh58.fsf@gnu.org> <87shvu1ixp.fsf@web.de> <8360spvn6i.fsf@gnu.org> <8760sjn5me.fsf@web.de> <871t37n51y.fsf@web.de> <8337nmon4l.fsf@gnu.org> <87mvluomaz.fsf@web.de> <83mvlun6zc.fsf@gnu.org> <83bn25fst6.fsf@gnu.org> <83vb0de91c.fsf@gnu.org> <87r3b12zcg.fsf@linux-m68k.org> <83mvlpe6n9.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1468176093 10550 80.91.229.3 (10 Jul 2016 18:41:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 10 Jul 2016 18:41:33 +0000 (UTC) Cc: michael_heerdegen@web.de, yasushi.shoji@gmail.com, me@wilfred.me.uk, npostavs@users.sourceforge.net, emacs-devel@gnu.org To: Eli Zaretskii , Andreas Schwab Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jul 10 20:41:22 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bMJfN-0005ws-Hr for ged-emacs-devel@m.gmane.org; Sun, 10 Jul 2016 20:41:21 +0200 Original-Received: from localhost ([::1]:56478 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bMJfM-0000FJ-LP for ged-emacs-devel@m.gmane.org; Sun, 10 Jul 2016 14:41:20 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35215) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bMJfG-0000ER-9i for emacs-devel@gnu.org; Sun, 10 Jul 2016 14:41:15 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bMJfE-0000zY-Dp for emacs-devel@gnu.org; Sun, 10 Jul 2016 14:41:13 -0400 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:35118) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bMJf9-0000y4-Jr; Sun, 10 Jul 2016 14:41:07 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 16087161454; Sun, 10 Jul 2016 11:41:06 -0700 (PDT) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 8HxGabL4RQeZ; Sun, 10 Jul 2016 11:41:05 -0700 (PDT) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 622E916145D; Sun, 10 Jul 2016 11:41:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ZXMUPQ9dtd-s; Sun, 10 Jul 2016 11:41:05 -0700 (PDT) Original-Received: from [192.168.1.64] (171.213.196.77.rev.sfr.net [77.196.213.171]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 97B09161454; Sun, 10 Jul 2016 11:41:02 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 In-Reply-To: <83mvlpe6n9.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 131.179.128.68 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:205519 Archived-At: On 07/10/2016 07:37 PM, Eli Zaretskii wrote: > Does the patch below fix the problem? Thanks. The patchfixes the problem for me; I reproduced it in an artificial environment using GCC 6. I think this fix should go into emacs-25, as it's small and isolated and clearly a fix and the failure symptoms are quite obscure(possibly already observed before but never pinned down).