This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: malloc attributes and realloc
- From: Robert Dewar <dewar at gnat dot com>
- To: Jeff Sturm <jsturm at one-point dot com>
- Cc: Daniel Berlin <dberlin at dberlin dot org>, gcc at gcc dot gnu dot org,"Joseph S. Myers" <jsm at polyomino dot org dot uk>
- Date: Thu, 01 Jan 2004 18:11:17 +0700
- Subject: Re: malloc attributes and realloc
- References: <Pine.LNX.4.44.0401011643450.25158-100000@ops2.one-point.com>
Nevertheless, the comment isn't quite right, isn't it? I was thinking of
the example "p1=malloc(n);free(p1);p2=malloc(n)" in which p1 == p2 is
possible even though they do not alias.
But after the free, p1 has an undefined value, and indeed the comparison
p1==p2 is undefined at that point, so it is certainly not something the
compiler has to worry about.