1run(1) GNU Tools run(1)
2
6 run—Simulator front-end
7
10 run [-v] [-p freq] [-m memory] [--sysroot filepath] program
11
13 Use `run program' to execute a binary by interpreting machine instruc‐
14 tions on your host computer.
15 run is the same emulator used by GDB's `target sim' command. You can
17 run it directly by executing run if you just want to see your program
18 execute, and do not need any debugger functionality. You can also use
19 run to generate profiling information for analysis with gprof.
20
23 -v Verbose output. Display the name of the program to run before
24 execution; after execution, display the number of instructions
25 executed, the number of machine cycles emulated, the number of
26 pipeline stalls, the real time taken, the emulated execution
27 time taken, and a summary of how much profiling information was
28 generated.
29 -p freq
32 Generate profile information (for use with gprof). freq is the
33 profiling frequency. Write the profiling information to a file
34 called gmon.out.
35 -m memory
38 Set the memory size for the emulated machine to two to the power
39 memory. The default value is 19, emulating a board with 524288
40 bytes of memory.
41 --sysroot filepath
44 Prepend filepath to all simulator system calls that pass abso‐
45 lute file paths. Change working directory to filepath at pro‐
46 gram start. Not all simulators support this option; those that
47 don't, will ignore it.
48
51 `gprof' entry in info; `gdb' entry in info; Using GDB: A Guide to the
52 GNU Source-Level Debugger, Richard M. Stallman and Roland H. Pesch.
53
56 Copyright (c) 1993-2015 Free Software Foundation, Inc.
57 This document is distributed under the terms of the GNU Free Documenta‐
59 tion License, version 1.1. That license is described in the sources
60 for this manual page, but it is not displayed here in order to make
61 this manual more consise. Copies of this license can also be obtained
62 from: http://www.gnu.org/copyleft/.
63GNU Tools 13oct1993 run(1)