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/106776] Unexpected use-after-free warning
Date: Sat, 22 Oct 2022 01:24:24 +0000	[thread overview]
Message-ID: <bug-106776-4-nDgBuljNDA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106776-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Here is a reduced testcase without any std::map or otherwise:
```
struct matrix_t
{
  int* count;

  matrix_t() :
    count(new int(1)) {}

  matrix_t(const matrix_t& p) :
    count(p.count) { ++*count; }

  ~matrix_t() { if (--*count == 0) { delete count;  } }
};

void f();
void cache1(void)
{
  matrix_t wftable;
  matrix_t wftable1(wftable);
  f();
}

```
basically what is going on is GCC cannot figure out the load from the count in
the first deconstructor will be greater than 1. GCC didn't inline the
deconstructor on the unwinding from exception which is causing GCC to think
count escapes and is read by f; the original case there is similar non-inlining
which is causing a similar issue.

The warning is a false positive but it is hard to prove unless you understand
the IR and such.

  parent reply	other threads:[~2022-10-22  1:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30  9:12 [Bug middle-end/106776] New: " drfiemost at email dot it
2022-08-30 16:34 ` [Bug middle-end/106776] " msebor at gcc dot gnu.org
2022-09-28 14:33 ` drfiemost at email dot it
2022-10-22  1:08 ` pinskia at gcc dot gnu.org
2022-10-22  1:24 ` pinskia at gcc dot gnu.org [this message]
2022-10-22  1:27 ` pinskia at gcc dot gnu.org
2023-05-30 17:03 ` drfiemost at yahoo dot com

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-106776-4-nDgBuljNDA@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).