From: "Giovanni Bajo" <giovannibajo@libero.it>
To: "Nick Ing-Simmons" <nick@ing-simmons.net>
Cc: <gcc@gcc.gnu.org>
Subject: Re: Optimizing of explicit temporary storage
Date: Wed, 13 Oct 2004 13:02:00 -0000 [thread overview]
Message-ID: <015501c4b11a$6ce74b60$18422597@bagio> (raw)
In-Reply-To: <20041013091948.4367.3@llama.elixent.com>
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
next prev parent reply other threads:[~2004-10-13 11:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 21:51 Richard Guenther
2004-10-11 4:34 ` Mike Stump
2004-10-11 7:11 ` Richard Guenther
2004-10-12 7:38 ` Mark Mitchell
2004-10-12 8:40 ` Florian Weimer
2004-10-12 9:37 ` Mark Mitchell
2004-10-12 11:59 ` Robert Dewar
2004-10-12 12:19 ` Mark Mitchell
2004-10-12 13:10 ` Robert Dewar
2004-10-12 19:44 ` Mike Stump
2004-10-13 2:27 ` Geoffrey Keating
2004-10-13 3:42 ` Daniel Berlin
2004-10-13 9:18 ` Chris Lattner
2004-10-13 10:47 ` Kai Henningsen
2004-10-13 13:22 ` Daniel Berlin
2004-10-13 16:06 ` Chris Lattner
2004-10-13 11:45 ` Nick Ing-Simmons
2004-10-13 13:02 ` Giovanni Bajo [this message]
2004-10-13 13:12 ` Nick Ing-Simmons
2004-10-14 4:21 ` Mike Stump
2004-10-12 9:02 ` Kai Henningsen
2004-10-12 19:36 ` Mike Stump
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='015501c4b11a$6ce74b60$18422597@bagio' \
--to=giovannibajo@libero.it \
--cc=gcc@gcc.gnu.org \
--cc=nick@ing-simmons.net \
/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).