This is the mail archive of the
mailing list for the GCC project.
Re: malloc attributes and realloc
Andreas Schwab <firstname.lastname@example.org> writes:
| Gabriel Dos Reis <email@example.com> writes:
| > Andreas Schwab <firstname.lastname@example.org> writes:
| > [...]
| > | > Even on an segmented architecture it needs to be possible to compare
| > | > pointers. If it were not necessary, why would realloc() docs talk about
| > | > "(possibly moved) block".
| > |
| > | The standard actually says "(which may have the same value as a
| > | pointer to the old object)". You can test for a subset of the "same
| > | value" condition by comparing the representation, and on an
| > | implementation where the indeterminate value of a pointer is never a
| > | trap representation you can even use == or !=, but that is not
| > | strictly compliant.
| > Well, the notion of "strictly conforming" is an oxymoron.
| s/strictly conforming/guaranteed by the standard/
By that do you include conforming programs?
If not, I can sympathize with Bruce's fears that GCC is heading the
wrong and dead road.