unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: David Ponce via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>, Eli Zaretskii <eliz@gnu.org>
Cc: 70568@debbugs.gnu.org
Subject: bug#70568: 30.0.50; build warnings on 'x86_64-pc-linux-gnu'
Date: Wed, 1 May 2024 09:18:27 +0200	[thread overview]
Message-ID: <4b847739-e5cf-46c2-a519-71452de978e3@orange.fr> (raw)
In-Reply-To: <7a34fb48-c1d3-470e-8078-04f9d106101e@cs.ucla.edu>

On 28/04/2024 00:20, Paul Eggert wrote:
> On 2024-04-27 02:37, Eli Zaretskii wrote:
>> Paul, are those real warnings, or just false alarms?
> Hard to say; someone who understands that part of the code would have to look at it in more detail.
> 
> I typically don't worry about these warnings unless they're generated by a default build (no 'configure' options except perhaps --enable-gcc-warnings) with the most recent GCC. This is because these warnings are usually false alarms these days, except perhaps for recently-added code.
> 
> On my list of things to do is to get Emacs to build with --enable-gcc-warnings and GCC 14, which is sort of out now (it's part of Fedora 40).

Since Paul committed changes to pacify GCC 14 warnings, Emacs builds cleanly.
For me this bug can be closed.

Thanks!





  parent reply	other threads:[~2024-05-01  7:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25 15:11 bug#70568: 30.0.50; build warnings on 'x86_64-pc-linux-gnu' David Ponce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-27  9:37 ` Eli Zaretskii
2024-04-27 22:20   ` Paul Eggert
2024-04-28  5:04     ` Eli Zaretskii
2024-04-28  5:05     ` Eli Zaretskii
2024-04-28  5:31       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-01  7:18     ` David Ponce via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-05-01  7:26       ` Paul Eggert

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=4b847739-e5cf-46c2-a519-71452de978e3@orange.fr \
    --to=bug-gnu-emacs@gnu.org \
    --cc=70568@debbugs.gnu.org \
    --cc=da_vid@orange.fr \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    /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).