From: Marc Glisse <marc.glisse@inria.fr>
To: sid@sourceware.org, newlib@sourceware.org,
gdb-patches@sourceware.org, binutils@sourceware.org,
gcc-patches@gcc.gnu.org
Subject: [libiberty] xmalloc cannot return NULL
Date: Mon, 14 Oct 2013 17:59:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1310141936460.4120@laptop-mg.saclay.inria.fr> (raw)
Hello,
libiberty provides a function xmalloc that never returns NULL. However,
there are some hints that it might be ok if someone wants to supply their
own xmalloc that can return NULL (though that would break a lot of things,
including in libiberty itself).
I would like to remove that freedom, and the point of this email (I hope
it doesn't bounce from too many of these addresses) is to ask all
libiberty users if that would cause problems for them. I already heard
from gcc and gdb that they are happy forbidding a null return value from
xmalloc.
Why do I want to do that? I just added an attribute "returns_nonnull" to
gcc and would like to mark relevant functions, to let the compiler
optimize based on this property.
http://gcc.gnu.org/ml/gcc-patches/2013-10/msg00817.html
--
Marc Glisse
next reply other threads:[~2013-10-14 17:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 17:59 Marc Glisse [this message]
2013-10-14 18:04 ` Mike Frysinger
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=alpine.DEB.2.10.1310141936460.4120@laptop-mg.saclay.inria.fr \
--to=marc.glisse@inria.fr \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=newlib@sourceware.org \
--cc=sid@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).