From: Andrew Haley <aph@redhat.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Question about -Wstrict-overflow=2
Date: Sat, 6 Mar 2021 11:23:33 +0000 [thread overview]
Message-ID: <e1709d54-b4a9-8aea-1925-e50c1381e6c8@redhat.com> (raw)
In-Reply-To: <20210306103703.GA10055@platinum.motzkau>
On 3/6/21 10:37 AM, Alexander Motzkau via Gcc-help wrote:
> So the question is what this warning is really about and how to get rid of
> it?
The compiler is telling you that it's assuming that expbuf + 120
does not wrap around. There's nothing really mysterious about it.
--
Andrew Haley (he/him)
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
https://keybase.io/andrewhaley
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
next prev parent reply other threads:[~2021-03-06 11:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 10:37 Alexander Motzkau
2021-03-06 11:23 ` Andrew Haley [this message]
2021-03-06 12:03 ` Alexander Motzkau
2021-03-07 11:37 ` Andrew Haley
2021-03-07 14:04 ` Alexander Motzkau
2021-03-07 14:56 ` Andrew Haley
2021-03-08 16:43 ` Segher Boessenkool
2021-03-07 15:31 ` Ian Lance Taylor
2021-03-08 21:05 ` Martin Sebor
2021-03-08 21:57 ` Alexander Motzkau
2021-03-09 9:09 ` Andrew Haley
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e1709d54-b4a9-8aea-1925-e50c1381e6c8@redhat.com \
--to=aph@redhat.com \
--cc=gcc-help@gcc.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.
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).