This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: malloc attributes and realloc


Andreas Schwab <schwab@suse.de> writes:

| Gabriel Dos Reis <gdr@integrable-solutions.net> writes:
| 
| > Andreas Schwab <schwab@suse.de> writes:
| >
| > | Gabriel Dos Reis <gdr@integrable-solutions.net> writes:
| > | 
| > | > Now, it is you who are confusing "free()ed" and "freed".
| > | > You have to be careful when reading the C standard :-)
| > | 
| > | The standard talks about allocation and deallocation of memory.
| > | Memory is allocated by malloc, calloc and realloc, and it is
| > | deallocated by free and realloc. 
| >
| > In user programs, yes.  The standard does NOT impose such requirements
| > on the implementation of the library.
| 
| And your point is? 

I thought I made it in a previous message -- its content is now entirely
absent from these subsequent followups, by a magic of snips :-(

| The implementation details of the C library are
| completely beyond (or sortof below) the scope of the standard.

Exactly.

-- Gaby


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]