From: Michael Matz <matz@suse.de>
To: Mike Stump <mrs@apple.com>
Cc: Marco Morandini <morandini@aero.polimi.it>, <gcc@gcc.gnu.org>,
<gcc-patches@gcc.gnu.org>
Subject: Re: PATCH: Re: A user question (was: Re: Faster compilation speed)
Date: Wed, 14 Aug 2002 04:42:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0208141341390.13269-100000@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0208141301070.13269-100000@wotan.suse.de>
On Wed, 14 Aug 2002, Michael Matz wrote:
> code you posted it seems, that the blocks bitmap is extremely sparse (in
> the second loop only one bit is set in evry case, the second loop only
^^^^^^
first of course
> seems to set one bit each time by pure luck), but still it's completely
Ciao,
Michael.
prev parent reply other threads:[~2002-08-14 4:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 10:34 Marco Morandini
2002-08-13 10:47 ` Marco Morandini
2002-08-13 14:29 ` Mike Stump
2002-08-13 17:06 ` PATCH: " Mike Stump
2002-08-13 19:53 ` Richard Henderson
2002-08-14 4:10 ` Michael Matz
2002-08-14 4:42 ` Michael Matz [this message]
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=Pine.LNX.4.33.0208141341390.13269-100000@wotan.suse.de \
--to=matz@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=morandini@aero.polimi.it \
--cc=mrs@apple.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).