From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Cc: Marc Glisse <marc.glisse@inria.fr>,
sid@sourceware.org, newlib@sourceware.org,
binutils@sourceware.org, gcc-patches@gcc.gnu.org
Subject: Re: [libiberty] xmalloc cannot return NULL
Date: Mon, 14 Oct 2013 18:04:00 -0000 [thread overview]
Message-ID: <201310141404.45773.vapier@gentoo.org> (raw)
In-Reply-To: <alpine.DEB.2.10.1310141936460.4120@laptop-mg.saclay.inria.fr>
[-- Attachment #1: Type: Text/Plain, Size: 1086 bytes --]
On Monday 14 October 2013 13:59:16 Marc Glisse wrote:
> 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
makes sense to me. as you point out, we write code based on the assumption
that NULL is never returned (although, perhaps phrased more accurately, that
the pointer returned is always valid).
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-10-14 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 17:59 Marc Glisse
2013-10-14 18:04 ` Mike Frysinger [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201310141404.45773.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=marc.glisse@inria.fr \
--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).