public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "i.maximets at ovn dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108187] False positive -Wfree-nonheap-object on impossible path with -O1
Date: Wed, 21 Dec 2022 11:51:47 +0000	[thread overview]
Message-ID: <bug-108187-4-8mErdStFeF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108187-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108187

--- Comment #3 from Ilya Maximets <i.maximets at ovn dot org> ---
(In reply to Ilya Maximets from comment #2)
> (In reply to Richard Biener from comment #1)
> > Well, between the store to ->source and the read from it is the call
> > to dp_packet_use_afxdp which gets &xpacket->packet as argument and thus
> > needs to be treated as clobbering ->source.  So GCC can indeed not know
> > that ->source is DPBUF_AFXDP since the path is not provable impossible.
> > dp_packet_use_afxdp doesn't even get a const struct dp_packet * argument
> > (not that this would semantically change things in C).
> 
> Hmm, dp_packet_use_afxdp() is the function that sets source to DPBUF_AFXDP
> and initializes other parts of the structure.  So, it cannot take a const
> argument.  If GCC just doesn't look inside the dp_packet_use_afxdp() function
> at all here, then it will indeed not know that the source is DPBUF_AFXDP now.

Clarification:  I realized that dp_packet_use_afxdp() is part of a different
translation unit, so GCC doesn't have a chance to know what this function is
doing, hence it doesn't know that source is DPBUF_AFXDP.  Though I don't know
how we can change that code to make GCC happy.  We'll likely end up just
disabling a warning.

> However, I'm not sure why the issue doesn't appear with -O0 then.

I'm still not sure why this is happening though.  Is there something
special about -O0 ?

  parent reply	other threads:[~2022-12-21 11:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20 14:33 [Bug c/108187] New: " i.maximets at ovn dot org
2022-12-21  7:53 ` [Bug tree-optimization/108187] " rguenth at gcc dot gnu.org
2022-12-21 10:44 ` i.maximets at ovn dot org
2022-12-21 11:51 ` i.maximets at ovn dot org [this message]
2022-12-21 18:05 ` pinskia 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-108187-4-8mErdStFeF@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).