public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/99098] invalid/missing -Wfree-nonheap-object warnings
Date: Wed, 30 Aug 2023 01:08:15 +0000 [thread overview]
Message-ID: <bug-99098-4-p9lcjqZdW9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99098-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99098
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Peter Ross from comment #2)
> The following test case produces a -Wfree-nonheap-object false positive. I
> argue that the memory being free'd is heap memory. It is offset by one to
> accomodate the negative offset applied immediately after malloc.
Doing -1 on an allocated memory location is undefined because you can only have
the address of 0...size to be taken of the "object" according to the C
standard. So the warning might seem wrong but you have undefined code
happening.
next prev parent reply other threads:[~2023-08-30 1:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 22:59 [Bug middle-end/99098] New: " msebor at gcc dot gnu.org
2021-02-14 23:05 ` [Bug middle-end/99098] " msebor at gcc dot gnu.org
2021-02-14 23:18 ` msebor at gcc dot gnu.org
2023-08-30 1:03 ` pross at xvid dot org
2023-08-30 1:05 ` pross at xvid dot org
2023-08-30 1:08 ` pinskia at gcc dot gnu.org [this message]
2023-08-30 1:30 ` pross at xvid dot org
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=bug-99098-4-p9lcjqZdW9@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).