From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11890 invoked by alias); 31 Jul 2002 19:53:29 -0000 Mailing-List: contact sid-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sid-owner@sources.redhat.com Received: (qmail 11882 invoked from network); 31 Jul 2002 19:53:28 -0000 Received: from unknown (HELO brouhaha.com) (209.66.107.17) by sources.redhat.com with SMTP; 31 Jul 2002 19:53:28 -0000 Received: (qmail 29246 invoked by uid 1032); 31 Jul 2002 19:53:37 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 31 Jul 2002 19:53:37 -0000 Date: Wed, 31 Jul 2002 12:53:00 -0000 From: Scott Dattalo X-X-Sender: sdattalo@ruckus.brouhaha.com To: sid@sources.redhat.com Subject: Profiling: --insn-count=1 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-q3/txt/msg00006.txt.bz2 To profile my simulated code, I've been invoking sid like so: arm-elf-sid --cpu arm --memory-region=0x2020000,0x2000000 \ --memory-region=0xfffe0000,0x1ffff --gdb=2000 --gprof \ --trace-counter --insn-count=1 -EL myprog I then simulate the application with arm-elf-gcc and examine the results with arm-elf-gprof. Now the question I have is there a way to count cpu cycles instead of cpu instructions? If there was a one-to-one relationship between the two, then it's not an issue. However, some instructions on the ARM are not single-cycled. I suppose the real question is, "is there a way to concisely measure the amount of 'simulated' time it take for a simulation to run?" FWIW, I'm using ~6 week old copy of SID. Scott