public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Rich Felker <dalias@libc.org>,
	 "Joseph S. Myers" <joseph@codesourcery.com>
Cc: "Rüdiger Sonderfeld" <ruediger@c-plusplus.de>, libc-alpha@sourceware.org
Subject: Re: [RFC][PATCH v2] Add reallocarray function.
Date: Tue, 20 May 2014 08:17:00 -0000	[thread overview]
Message-ID: <537AEC86.7040306@cs.ucla.edu> (raw)
In-Reply-To: <20140520020108.GV507@brightrain.aerifal.cx>

Rich Felker wrote:
> Not really related to this patch, but I think the comment about
> __attribute_malloc__ that was copied from realloc is wrong. The new
> and old pointers cannot alias

You're correct that the new and old pointers cannot alias, but I fear 
that __attribute_malloc__ does not mean what you think it means.  The 
GCC documentation is *really* confusing in this area, unfortunately.

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

  reply	other threads:[~2014-05-20  5:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-18 21:05 [RFC][PATCH] " Rüdiger Sonderfeld
2014-05-18 21:43 ` Paul Eggert
2014-05-18 21:50   ` [RFC][PATCH v2] " Rüdiger Sonderfeld
2014-05-19  4:27     ` Rüdiger Sonderfeld
2014-05-19 15:30     ` Joseph S. Myers
2014-05-20  4:35       ` Rich Felker
2014-05-20  8:17         ` Paul Eggert [this message]
2014-05-20  8:19         ` Andreas Schwab
2014-05-20 15:45           ` Paul Eggert
2014-05-20 20:47             ` Rich Felker
2014-05-20 20:56               ` Paul Eggert
2014-05-20 12:50       ` Rüdiger Sonderfeld
2014-05-20 14:18         ` Paul Eggert
2014-05-21 12:39           ` Rüdiger Sonderfeld
2014-05-22  5:45             ` Paul Eggert
2014-09-01 15:48 ` [RFC][PATCH] " Florian Weimer
2014-09-01 17:24   ` Rich Felker
2014-09-02  9:29     ` Florian Weimer
2014-09-02 13:03       ` Rich Felker

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=537AEC86.7040306@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=dalias@libc.org \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=ruediger@c-plusplus.de \
    /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).