From: dewar@gnat.com
To: guerby@acm.org, zack@codesourcery.com
Cc: gcc@gcc.gnu.org
Subject: Re: The bloat sweepstakes...
Date: Sun, 07 Oct 2001 15:21:00 -0000 [thread overview]
Message-ID: <20011007222105.AF45FF28AE@nile.gnat.com> (raw)
<<Surely there's some form of dynamic allocation you could use for this,
though. Or just not buffering the file in such huge chunks? C stdio
tends to use buffers on the order of a memory page...
>>
Would this really gain? Are there really systems so messed up that large
unused buffers like this cost real disk space or real memory?
next reply other threads:[~2001-10-07 15:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-07 15:21 dewar [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-08 10:07 dewar
2001-10-08 11:04 ` Zack Weinberg
2001-10-08 10:03 dewar
2001-10-08 10:01 dewar
2001-10-07 15:24 dewar
2001-10-07 15:16 dewar
2001-10-08 9:59 ` Zack Weinberg
2001-10-07 10:25 Zack Weinberg
2001-10-07 10:44 ` guerby
2001-10-07 11:26 ` Zack Weinberg
2001-10-07 11:44 ` guerby
2001-10-07 12:43 ` Zack Weinberg
2001-10-07 14:42 ` guerby
2001-10-09 23:24 ` Fergus Henderson
2001-10-10 15:09 ` Zack Weinberg
2001-10-10 23:03 ` Fergus Henderson
2001-10-10 23:46 ` Zack Weinberg
2001-10-19 9:43 ` law
2001-10-22 0:39 ` Zack Weinberg
2001-10-22 8:28 ` law
2001-10-22 15:01 ` Richard Henderson
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=20011007222105.AF45FF28AE@nile.gnat.com \
--to=dewar@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=guerby@acm.org \
--cc=zack@codesourcery.com \
/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).