From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: Emacs 27.0.90 is out! Date: Thu, 5 Mar 2020 18:18:28 -0800 Organization: UCLA Computer Science Department Message-ID: <81219522-2847-5585-c678-4b16376d47aa@cs.ucla.edu> References: <87wo814p3a.fsf@petton.fr> <874kv5o8t1.fsf@moondust.localdomain> <831rq7wbhw.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="31879"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 Cc: nljlistbox2@gmail.com, emacs-devel@gnu.org, nico@petton.fr To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Mar 06 03:20:05 2020 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 1jA2ar-0008F7-Iv for ged-emacs-devel@m.gmane-mx.org; Fri, 06 Mar 2020 03:20:05 +0100 Original-Received: from localhost ([::1]:58672 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jA2aq-0004Vj-LN for ged-emacs-devel@m.gmane-mx.org; Thu, 05 Mar 2020 21:20:04 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53705) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jA2ZQ-0002dC-86 for emacs-devel@gnu.org; Thu, 05 Mar 2020 21:18:37 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jA2ZO-0007Ie-BG for emacs-devel@gnu.org; Thu, 05 Mar 2020 21:18:35 -0500 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:56380) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1jA2ZM-0007Ao-Sk; Thu, 05 Mar 2020 21:18:33 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 39137160092; Thu, 5 Mar 2020 18:18:29 -0800 (PST) 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 OtNUmrHUKTkw; Thu, 5 Mar 2020 18:18:28 -0800 (PST) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 72A8016009A; Thu, 5 Mar 2020 18:18:28 -0800 (PST) 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 gybwGAU_rQ_S; Thu, 5 Mar 2020 18:18:28 -0800 (PST) Original-Received: from Penguin.CS.UCLA.EDU (Penguin.CS.UCLA.EDU [131.179.64.200]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 5361E160092; Thu, 5 Mar 2020 18:18:28 -0800 (PST) In-Reply-To: <831rq7wbhw.fsf@gnu.org> Content-Language: en-US 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.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:245281 Archived-At: On 3/4/20 10:40 PM, Eli Zaretskii wrote: > I'm not yet sure which part(s) of the changeset directly shut up the > "-Walloc-size-larger-than=N" warnings. Is that the part that adds the > calls to 'assume'? Yes. > If so, we already call eassume in many places; it > won't be a problem to add a few more, and fix the warnings on the > emacs-27 branch. I'd rather not backport this stuff into the emacs-27 branch, since the eassume calls do not fix bugs and can change the code generated and therefore can inadvertently introduce bugs. People building on emacs-27 can either live with the warnings, or use ordinary GCC options instead of unusual ones, or not enable warnings. Pacifying GCC when Emacs is built with unusual options is a low-priority thing to do, as we can't feasibly pacify GCC's false alarms under every option combination (there are far too many combinations and pacifying GCC in every instance would cause make-work maintenance and complicate Emacs and wouldn't make Emacs more reliable). Instead, we should merely suggest to people to not enable GCC warnings when they are employing unusual GCC options. > And what about a similar warning I reported in bug#39857? That's a false alarm, and I suppose it's a bug in the particular GCC build that you used. I expect the simplest workaround is stick to the usual compiler options (i.e., avoid -Og), or to disable GCC warnings. For what it's worth I can't reproduce the problem on Fedora 31 x86 (i.e., 32-bit) with GCC 9.2.1 20190827 (Red Hat 9.2.1-1), so perhaps you can work around the problem by using a newer GCC.