From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: nljlistbox2@gmail.com, emacs-devel@gnu.org, nico@petton.fr
Subject: Re: Emacs 27.0.90 is out!
Date: Thu, 05 Mar 2020 08:40:11 +0200 [thread overview]
Message-ID: <831rq7wbhw.fsf@gnu.org> (raw)
In-Reply-To: <d351bf38-8cd6-b58b-f31d-931c038d0a91@cs.ucla.edu> (message from Paul Eggert on Wed, 4 Mar 2020 13:51:03 -0800)
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Wed, 4 Mar 2020 13:51:03 -0800
> Cc: Emacs Devel <emacs-devel@gnu.org>
>
> On 3/3/20 5:40 AM, N. Jackson wrote:
> > It's very nice to build an Emacs with so few warnings! Are the
> > -Walloc-size-larger-than= warnings expected?
>
> Not really. I reproduced the problem in master (along with some other
> warnings) and installed the attached patch to master to fix them. I
> doubt whether this is worth backporting to Emacs 27. If you compile with
> -O2 rather than -O3 the false alarms (and one true alarm :-) should go away.
Thanks.
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'? 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.
And what about a similar warning I reported in bug#39857?
next prev parent reply other threads:[~2020-03-05 6:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 12:09 Emacs 27.0.90 is out! Nicolas Petton
2020-03-03 13:40 ` N. Jackson
2020-03-03 16:09 ` Eli Zaretskii
2020-03-03 16:30 ` N. Jackson
2020-03-04 21:51 ` Paul Eggert
2020-03-05 6:40 ` Eli Zaretskii [this message]
2020-03-06 2:18 ` Paul Eggert
2020-03-04 3:21 ` Richard Stallman
2020-03-04 3:40 ` Eli Zaretskii
2020-03-05 8:12 ` Philippe Vaucher
2020-03-05 13:52 ` Pieter van Oostrum
2020-03-05 14:19 ` Noam Postavsky
2020-03-06 15:25 ` Pieter van Oostrum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=831rq7wbhw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=nico@petton.fr \
--cc=nljlistbox2@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).