unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: David Fussner <dfussner@googlemail.com>
Cc: 47518@debbugs.gnu.org
Subject: bug#47518: 28.0.50; gcc 5.5.0 -Wstrict-overflow warning in INT_ADD_WRAPV
Date: Sat, 08 May 2021 14:08:26 +0200	[thread overview]
Message-ID: <8735uxsa11.fsf@gnus.org> (raw)
In-Reply-To: <CADF+RthX8DJtG01uR-njt=MbXq46nh5BGqX=ShyUcScm6Yk2rA@mail.gmail.com> (David Fussner's message of "Wed, 31 Mar 2021 11:12:29 +0100")

David Fussner <dfussner@googlemail.com> writes:

> Since late December, when compiling master with gcc 5.5.0 on a 32-bit
> Slackware install I see multiple warnings like the following.  _All_
> of the messages involve INT_ADD_WRAPV:
>
> In file included from dispnew.c:27:0:
> lisp.h: In function 'modiff_incr':
> lisp.h:3505:3: warning: assuming signed overflow does not occur when
> assuming that (X + c) > X is always true [-Wstrict-overflow]
>    bool modiff_overflow = INT_ADD_WRAPV (a0, 1, a);
>    ^
> (This last from every .c file that includes lisp.h.)

It's to be expected to get warnings in older gcc versions for a variety
of things -- and gcc 5.5.0 is five years old.  We don't have a strict
policy for this in Emacs, but it's been common to disregard warnings
from gcc versions that are a few years old.

So I'm closing this bug report.  If somebody thinks that this is
something that should be worked on, please respond to the debbugs
address and we'll reopen.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-05-08 12:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-31 10:12 bug#47518: 28.0.50; gcc 5.5.0 -Wstrict-overflow warning in INT_ADD_WRAPV David Fussner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-08 12:08 ` Lars Ingebrigtsen [this message]
2021-05-08 12:09   ` Lars Ingebrigtsen

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=8735uxsa11.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=47518@debbugs.gnu.org \
    --cc=dfussner@googlemail.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).