This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Optimizing of explicit temporary storage
Nick Ing-Simmons wrote:
>> it would be surprising to most programmers to optimize away the call
>> because malloc *does* have side-effects on real systems. For
>> example, on UNIX, it is likely to call sbrk, which result in
>> observable changes in the process state.
>
> Indeed! - I have actually written
>
> free(malloc(estimated_total_need));
>
> To get expensive sbrk() call out of the way with one big one
> rather than many smaller ones.
So why not calling sbrk() directly?
Giovanni Bajo