From: Siddhesh Poyarekar via Libc-alpha <libc-alpha@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v2] xmalloc: Fix warnings with gcc analyzer
Date: Wed, 28 Jul 2021 16:57:34 +0530 [thread overview]
Message-ID: <16ac6a84-3425-0688-1718-cb35bffae001@sourceware.org> (raw)
In-Reply-To: <87o8am8yub.fsf@oldenburg.str.redhat.com>
On 7/28/21 4:55 PM, Florian Weimer wrote:
> So it does not free anything ever?
Specifically, it does not act as a substitute for free(); it does free
during reallocation.
> We should not have two different attributes for xrealloc. I suggest to
> drop the attribute from the include/* version for now, until we can
> clean this up.
OK. Perhaps it would make sense to consolidate the two x* functions too
later. I'll post v3.
Siddhesh
prev parent reply other threads:[~2021-07-28 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 10:33 [PATCH v2] xmalloc: Fix warnings with gcc analyzer Siddhesh Poyarekar via Libc-alpha
2021-07-28 11:14 ` Florian Weimer via Libc-alpha
2021-07-28 11:23 ` Siddhesh Poyarekar via Libc-alpha
2021-07-28 11:25 ` Florian Weimer via Libc-alpha
2021-07-28 11:27 ` Siddhesh Poyarekar via Libc-alpha [this message]
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16ac6a84-3425-0688-1718-cb35bffae001@sourceware.org \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.com \
--cc=siddhesh@sourceware.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).