From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sid-return-374-listarch-sid=sources.redhat.com@sources.redhat.com>
Received: (qmail 13707 invoked by alias); 1 Aug 2002 16:00:32 -0000
Mailing-List: contact sid-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:sid-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/sid/>
List-Post: <mailto:sid@sources.redhat.com>
List-Help: <mailto:sid-help@sources.redhat.com>, <http://sources.redhat.com/lists.html#faqs>
Sender: sid-owner@sources.redhat.com
Received: (qmail 13700 invoked from network); 1 Aug 2002 16:00:30 -0000
Received: from unknown (HELO brouhaha.com) (209.66.107.17)
  by sources.redhat.com with SMTP; 1 Aug 2002 16:00:30 -0000
Received: (qmail 24545 invoked by uid 1032); 1 Aug 2002 16:00:39 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 1 Aug 2002 16:00:39 -0000
Date: Thu, 01 Aug 2002 09:00:00 -0000
From: Scott Dattalo <scott@dattalo.com>
X-X-Sender: sdattalo@ruckus.brouhaha.com
cc: sid@sources.redhat.com
Subject: Re: Profiling: --insn-count=1
In-Reply-To: <20020801113202.C16668@redhat.com>
Message-ID: <Pine.LNX.4.44.0208010857390.22716-100000@ruckus.brouhaha.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-SW-Source: 2002-q3/txt/msg00010.txt.bz2

On Thu, 1 Aug 2002, Frank Ch. Eigler wrote:

> To get the most precise answer, you'd best use hardware running a
> profiling-capable OS.  If accounting for approximate memory latencies
> is good enough, then SID can be of help.

Agreed. The whole purpose of simulation in my case is to obtain a
relatively accurate assessment of the hardware requirements. Believe me,
hardware is coming... And I should add SID has been invaluable! Thanks.

Scott