public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105346] -Wno-free-nonheap-object false positive (on Bison-generated grammar code)
Date: Tue, 26 Apr 2022 09:40:36 +0000 [thread overview]
Message-ID: <bug-105346-4-G49NldHhlh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105346-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105346
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
Keywords| |diagnostic
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Tim Van Holder from comment #4)
> Marking as C++ rather than C; while Bison generates C code, here it gets
> compiled in C++ context (with a namespace wrapped around Bison's symbols).
Thanks, I can confirm the diagnostic with -O0, it goes away when optimizing.
The issue seems to be that yyss (or yymsg) are not assigned to anywhere
in the function and so we essentially have
void foo()
{
char buf[20];
char *bufp = buf;
if (bufp != buf)
free (bufp);
}
which we diagnose. When optimizing the test is optimized away.
next prev parent reply other threads:[~2022-04-26 9:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 12:12 [Bug c/105346] New: " tim.vanholder at anubex dot com
2022-04-22 12:21 ` [Bug c/105346] " rguenth at gcc dot gnu.org
2022-04-26 8:10 ` tim.vanholder at anubex dot com
2022-04-26 9:20 ` tim.vanholder at anubex dot com
2022-04-26 9:21 ` [Bug c++/105346] " tim.vanholder at anubex dot com
2022-04-26 9:40 ` rguenth at gcc dot gnu.org [this message]
2022-04-26 9:52 ` [Bug middle-end/105346] " rguenth at gcc dot gnu.org
2022-04-26 9:53 ` [Bug middle-end/105346] [11/12 Regression] " rguenth at gcc dot gnu.org
2022-04-26 9:56 ` jakub at gcc dot gnu.org
2022-04-26 10:09 ` rguenther at suse dot de
2022-04-26 10:12 ` jakub at gcc dot gnu.org
2022-04-26 13:53 ` amacleod at redhat dot com
2022-04-26 14:12 ` aldyh at gcc dot gnu.org
2022-04-27 7:15 ` rguenth at gcc dot gnu.org
2022-04-27 9:06 ` aldyh at gcc dot gnu.org
2022-04-27 9:16 ` rguenth at gcc dot gnu.org
2022-04-27 9:23 ` aldyh at gcc dot gnu.org
2022-04-27 10:17 ` rguenth at gcc dot gnu.org
2023-05-29 10:06 ` [Bug middle-end/105346] [11/12/13/14 " jakub at gcc dot gnu.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-105346-4-G49NldHhlh@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).