unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Jose A. Ortega Ruiz" <jao@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: warnings compiling emacs28 with gcc 12.1
Date: Thu, 28 Jul 2022 20:13:40 +0200	[thread overview]
Message-ID: <87tu71umuj.fsf@gnus.org> (raw)
In-Reply-To: <874jz1up5c.fsf@mail.jao.io> (Jose A. Ortega Ruiz's message of "Thu, 28 Jul 2022 18:23:59 +0100")

"Jose A. Ortega Ruiz" <jao@gnu.org> writes:

> Fair enough.  A curious fact is that the master branch compiles cleanly
> with the same GCC version, without any warning at all in fact.  I guess
> someone already took the time to pacify non-sense warnings.

Yes, they were fixed on the trunk by:

commit 0f731c49e6a8ccf3aa4c30c3f8ca82ed0a2cefb7
Author:     Paul Eggert <eggert@cs.ucla.edu>
AuthorDate: Thu May 12 17:01:10 2022 -0700

    Pacify GCC 12 in default developer build

For instance:

    * src/term.c (Fsuspend_tty): Don’t look at a pointer after freeing
    it, even just to test it for equality with some other pointer, as
    this has undefined behavior in C and GCC 12 diagnoses this.



      reply	other threads:[~2022-07-28 18:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28  3:32 warnings compiling emacs28 with gcc 12.1 Jose A. Ortega Ruiz
2022-07-28 17:02 ` Eli Zaretskii
2022-07-28 17:12   ` Óscar Fuentes
2022-07-28 17:38     ` Eli Zaretskii
2022-07-28 18:31       ` Andreas Schwab
2022-07-28 18:35       ` Óscar Fuentes
2022-07-28 17:23   ` Jose A. Ortega Ruiz
2022-07-28 18:13     ` Lars Ingebrigtsen [this message]

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=87tu71umuj.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=jao@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).