public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pross at xvid dot 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:03:59 +0000	[thread overview]
Message-ID: <bug-99098-4-fxcpX8TkeF@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

Peter Ross <pross at xvid dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pross at xvid dot org

--- Comment #2 from Peter Ross <pross at xvid dot org> ---
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.

```
#include <stdlib.h>
char * knn_alloc()
{
    char * w = malloc(sizeof(char));
    if (!w)
        return NULL;
    return w - 1;
}
void knn_free(char * w)
{
    free(w + 1);
}
int main()
{
    char * w = knn_alloc();
    if (!w)
        return -1;

    knn_free(w);
    return 0;
}
```

```
$ gcc knn.c -save-temps
knn.c: In function ‘knn_free’:
knn.c:11:5: warning: ‘free’ called on pointer ‘w’ with nonzero offset 1
[-Wfree-nonheap-object]
   11 |     free(w + 1);
      |     ^~~~~~~~~~~

```

gcc --version: gcc (Debian 13.2.0-2) 13.2.0
uname -a: Linux computer 6.4.0-3-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.4.11-1
(2023-08-17) x86_64 GNU/Linux

  parent reply	other threads:[~2023-08-30  1:04 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 [this message]
2023-08-30  1:05 ` pross at xvid dot org
2023-08-30  1:08 ` pinskia at gcc dot gnu.org
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-fxcpX8TkeF@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).