📄 test-mat.sim
字号:
sim-eio: SimpleScalar/Alpha Tool Set version 3.0 of September, 1998.Copyright (c) 1994-1998 by Todd M. Austin. All Rights Reserved.warning: section `.comment' ignored...sim: tracing execution to EIO file `eio/test-math.eio'...sim: command line: ../sim-eio -trace eio/test-math.eio -redir:sim outputs/test-math.simout -redir:prog outputs/test-math.progout bin/test-math sim: simulation started @ Wed Aug 26 17:02:01 1998, options follow:sim-eio: This simulator implements simulator support for generatingexternal event traces (EIO traces) and checkpoint files. Externalevent traces capture one execution of a program, and allow it to bepackaged into a single file for later re-execution. EIO trace executionsare 100% reproducible between subsequent executions (on the same platform.This simulator also provides functionality to generate checkpoints atarbitrary points within an external event trace (EIO) execution. Thecheckpoint file (along with the EIO trace) can be used to start anySimpleScalar simulator in the middle of a program execution.# -config # load configuration from a file# -dumpconfig # dump configuration to a file# -h false # print help message # -v false # verbose operation # -d false # enable debug message # -i false # start in Dlite debugger-seed 1 # random number generator seed (0 for timer seed)# -q false # initialize and terminate immediately# -chkpt <null> # restore EIO trace execution from <fname># -redir:sim outputs/test-math.simout # redirect simulator output to file (non-interactive only)# -redir:prog outputs/test-math.progout # redirect simulated program output to file-nice 0 # simulator scheduling priority-max:inst 0 # maximum number of inst's to execute-fastfwd 0 # number of insts skipped before tracing starts-trace eio/test-math.eio # EIO trace file output file name# -dump <null> # specify checkpoint file and trigger: <fname> <range> Checkpoint range triggers are formatted as follows: {{@|#}<start>}:{{@|#|+}<end>} Both ends of the range are optional, if neither are specified, the range triggers immediately. Ranges that start with a `@' designate an address range to trigger on, those that start with an `#' designate a cycle count trigger. All other ranges represent an instruction count range. The second argument, if specified with a `+', indicates a value relative to the first argument, e.g., 1000:+100 == 1000:1100. Examples: -ptrace FOO.trc #0:#1000 -ptrace BAR.trc @2000: -ptrace BLAH.trc :1500 -ptrace UXXE.trc :sim: writing EIO file initial checkpoint...sim: ** starting functional simulation **warning: partially supported sigprocmask() call...sim: ** simulation statistics **sim_num_insn 49313 # total number of instructions executedsim_num_refs 13601 # total number of loads and stores executedsim_elapsed_time 1 # total simulation time in secondssim_inst_rate 49313.0000 # simulation speed (in insts/sec)ld_text_base 0x0120000000 # program text (code) segment baseld_text_size 188416 # program text (code) size in bytesld_data_base 0x0140000000 # program initialized data segment baseld_data_size 41984 # program init'ed `.data' and uninit'ed `.bss' size in bytesld_stack_base 0x011ff9b000 # program stack segment base (highest address in stack)ld_stack_size 16384 # program initial stack sizeld_prog_entry 0x012000f750 # program entry point (initial PC)ld_environ_base 0x011ff97000 # program environment base address addressld_target_big_endian 0 # target executable endian-ness, non-zero if big endianmem.page_count 28 # total number of pages allocatedmem.page_mem 224k # total size of memory pages allocatedmem.ptab_misses 74 # total first level page table missesmem.ptab_accesses 482033 # total page table accessesmem.ptab_miss_rate 0.0002 # first level page table miss rate
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -