From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: Suspicious warning in W64 build Date: Sat, 16 Sep 2017 23:40:05 -0700 Organization: UCLA Computer Science Department Message-ID: <9b9bfa40-a248-ed77-6522-53fe73e55434@cs.ucla.edu> References: <1017454172.910810.1504618695244@mail.libero.it> <83mv66z66p.fsf@gnu.org> <102a4c21-c275-c73e-ec53-0d85975dc968@cs.ucla.edu> <83a825znuf.fsf@gnu.org> <831snhzkgw.fsf@gnu.org> <837ex9x7vf.fsf@gnu.org> <83tw0cwcle.fsf@gnu.org> <83h8wcw3td.fsf@gnu.org> <83377vx3d0.fsf@gnu.org> <83ingnq01t.fsf@gnu.org> <83fubrpxsv.fsf@gnu.org> <83r2v9masw.fsf@gnu.org> <83d16smj5o.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1505630428 17838 195.159.176.226 (17 Sep 2017 06:40:28 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 17 Sep 2017 06:40:28 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 Cc: fabrice.popineau@centralesupelec.fr, emacs-devel@gnu.org To: Eli Zaretskii , Richard Copley Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Sep 17 08:40:20 2017 Return-path: Envelope-to: ged-emacs-devel@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 1dtTFZ-0004IT-6J for ged-emacs-devel@m.gmane.org; Sun, 17 Sep 2017 08:40:17 +0200 Original-Received: from localhost ([::1]:59557 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dtTFg-0004MM-AL for ged-emacs-devel@m.gmane.org; Sun, 17 Sep 2017 02:40:24 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58823) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dtTFa-0004MF-Mh for emacs-devel@gnu.org; Sun, 17 Sep 2017 02:40:19 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dtTFZ-0005Ec-TQ for emacs-devel@gnu.org; Sun, 17 Sep 2017 02:40:18 -0400 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:60094) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dtTFT-000578-Sm; Sun, 17 Sep 2017 02:40:12 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 60474160D37; Sat, 16 Sep 2017 23:40: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 P_pDpB9a6-rH; Sat, 16 Sep 2017 23:40:05 -0700 (PDT) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id A0D35160D3B; Sat, 16 Sep 2017 23:40: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 3HKmfbECxtDz; Sat, 16 Sep 2017 23:40:05 -0700 (PDT) Original-Received: from [192.168.1.9] (unknown [47.154.18.85]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 755B91608AA; Sat, 16 Sep 2017 23:40:05 -0700 (PDT) In-Reply-To: <83d16smj5o.fsf@gnu.org> Content-Language: en-US X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] 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:218389 Archived-At: Eli Zaretskii wrote: > Not sure what to do about this. Add 'volatile' to the declaration of > 'c'? Looks like a GCC bug. To work around it, please try CACHEABLE instead of=20 volatile, to warn the reader that it's a compiler-bug workaround. Like th= is: struct handler *CACHEABLE c =3D handlerlist->nextfree; > This seems to imply that m4/manywarnings.m4 has a bug: it somehow > deduces that a 64-bit Windows build can only allocate up to LONG_MAX > bytes. That is due to a limitation in AC_COMPUTE_INT: it can't handle numbers la= rger=20 than LONG_MAX. I attempted to work around this limitation by changing Gnu= lib to=20 assume that the correct value is 2**63 - 1 if it doesn't fit in 'long', a= nd by=20 merging the latest Gnulib into the emacs-26 branch. Please give it a try.