From: Thomas Neumann <thomas.neumann@in.tum.de>
To: gcc-patches@gcc.gnu.org
Subject: PING: [PATCH] release the sorted FDE array when deregistering a frame [PR109685]
Date: Fri, 12 May 2023 17:19:47 +0200 [thread overview]
Message-ID: <13233832-d564-6007-f890-53e7e6df2ca6@in.tum.de> (raw)
Summary: The old linear scan logic called free while searching the list
of frames. The atomic fast path finds the frame quickly, but forgot the
free call. This patches adds the missing free. Bugzilla #109685.
See:
https://gcc.gnu.org/pipermail/gcc-patches/2023-May/617245.html
Best
Thomas
next reply other threads:[~2023-05-12 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 15:19 Thomas Neumann [this message]
2023-05-19 17:26 ` Jeff Law
2023-05-19 18:50 ` [PATCH v2] " Thomas Neumann
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=13233832-d564-6007-f890-53e7e6df2ca6@in.tum.de \
--to=thomas.neumann@in.tum.de \
--cc=gcc-patches@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).