Waiting mail (msg.aa10287)

[top Mail System (MMDF)]

    After 3 days (63 hours), your message has not yet been
fully delivered.  Attempts to deliver the message will continue
for 8 more days.  No further action is required by you.

    Delivery attempts are still pending for the following address(es):

	fadushin

    Problems usually are due to service interruptions at the receiving
machine.  Less often, they are caused by the communication system.

    Your message begins as follows:

Received: from rufus.w3.org by lohengrin.top.cis.syr.edu id aa10287;
          16 Jul 98 13:32 EDT
Received: from localhost (majordom@localhost [127.0.0.1])
	by rufus.w3.org (8.8.7/8.8.7) with SMTP id NAA31119;
	Thu, 16 Jul 1998 13:32:03 -0400
Received: (from majordom@localhost)
	by rufus.w3.org (8.8.7/8.8.7) id NAA30940
	for kaffe-outgoing; Thu, 16 Jul 1998 13:30:33 -0400
Resent-Date: Thu, 16 Jul 1998 13:30:33 -0400
Resent-Message-Id: <199807161730.NAA30940@rufus.w3.org>
X-Authentication-Warning: sundance.cse.ucsc.edu: charlie owned process doing -bs
Date: Thu, 16 Jul 1998 10:30:26 -0700 (PDT)
From: Charlie McDowell <charlie@cse.ucsc.edu>
To: kaffe@rufus.w3.org
Subject: ByteCode Frequency data wanted
In-Reply-To: <199807142313.RAA01013@sal.cs.utah.edu>
Message-ID: <Pine.GSO.3.96.980716102930.22309E-100000@sundance.cse.ucsc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-kaffe@rufus.w3.org
Precedence: bulk
Reply-To: kaffe@rufus.w3.org
Errors-To: kaffe-error@rufus.w3.org
X-loop: kaffe@rufus.w3.org
X-mailing-list: kaffe@rufus.w3.org
Resent-from: kaffe@rufus.w3.org

Sorry, this isn't exactly a kaffe question, but I'm working with kaffe and
I'd like to know if anyone knows about any dynamic bytecode frequency
...