From: Eli Zaretskii <eliz@gnu.org>
To: "N. Jackson" <njackson@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: pdumper.c Wstringop-overflow warnings with CFLAGS="-O3" [Re: Emacs 29.2 released]
Date: Fri, 19 Jan 2024 09:23:44 +0200 [thread overview]
Message-ID: <83il3pwzun.fsf@gnu.org> (raw)
In-Reply-To: <87a5p23xtc.fsf@moondust.localdomain> (njackson@posteo.net)
> From: "N. Jackson" <njackson@posteo.net>
> Date: Fri, 19 Jan 2024 01:40:31 +0000
>
>
> At 13:06 +0200 on Thursday 2024-01-18, Eli Zaretskii wrote:
> >
> > Version 29.2 of Emacs, the extensible text editor, should now
> > be available
>
> Thank you Eli for your stalwart maintenance of Emacs and to everyone
> else who has contributed recently (and, indeed, ever).
>
> Building Emacs 29.2 with CFLAGS="-O3" I get four Wstringop-overflow
> warnings in pdumper.c (see below). Can I (as an Emacs user) safely
> ignore these warnings? Note: I don't get these warnings with
> CFLAGS="-O2".
If someone wants to investigate these warnings, please do. My sincere
suggestion is not to build Emacs with -O3 regardless: it is not going
to give you a faster Emacs, and might even give you a slower Emacs.
That's because the inner-most loops in Emacs are very large, and the
optimization techniques used by -O3 are likely not to work well, while
at the same time the excessive inlining might make those loops larger
and thus overflow the CPU caches, which slows down code execution.
Thanks.
next prev parent reply other threads:[~2024-01-19 7:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 11:06 Emacs 29.2 released Eli Zaretskii
2024-01-18 12:06 ` Po Lu
2024-01-18 12:27 ` Eli Zaretskii
2024-01-18 12:38 ` Po Lu
2024-01-18 13:00 ` Eli Zaretskii
2024-01-20 14:41 ` Eli Zaretskii
2024-01-22 6:20 ` Po Lu
2024-01-23 17:41 ` Eli Zaretskii
2024-01-19 1:40 ` pdumper.c Wstringop-overflow warnings with CFLAGS="-O3" [Re: Emacs 29.2 released] N. Jackson
2024-01-19 7:23 ` Eli Zaretskii [this message]
2024-01-19 21:22 ` Emacs 29.2 released Michael Albinus
2024-01-20 6:51 ` Eli Zaretskii
2024-01-20 8:17 ` Michael Albinus
2024-01-20 9:01 ` Eli Zaretskii
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=83il3pwzun.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=njackson@posteo.net \
/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).