1) To install Feldstein SPARC-V9 Simulator, download one of the packages below. These packages are for systems that already have Java 6 installed. If Java is not already installed, you might be able to download it for your system from java.com. (Warning to Windows users: A failure has been observed with both Internet Explorer and Firefox that causes the package filename to be modified on download.)
| Release | Download Package | Size |
|---|---|---|
| Version_0-000 |
 |
41 KiB |
| Version_0-001 |
|
42 KiB |
| Version_0-002 |
|
39 KiB |
| Version_0-003 |
|
43 KiB |
| Version_0-004 |
|
57 KiB |
| Version_0-005 |
|
59 KiB |
| Version_0-006 |
|
90 KiB |
2) Once you have downloaded the package, uncompress the file and extract that output into the current directory. For example:
$ gzcat Feldstein_SPARC-V9_Simulator_Version_0-006.tar.gz | tar xf -
WinZip also supports TAR files compressed in GZ format.
3) Ensure that the /opt directory exists. Then move the extracted software into the /opt directory. For example:
$ mv fss /opt
This will create the /opt/fss directory. We use /opt/fss as an example. Feldstein SPARC-V9 Simulator can be installed in any location.
4) If the system requirements have been met, you can now run Feldstein SPARC-V9 Simulator. For example:
$ cd /opt/fss $ java -d64 -cp fss.jar:table.jar:JHDL.jar:axis2-adb-1.2.jar:derby.jar com.alanfeldstein.sparc.fss.SparcCaseStudy &
(The above example assumes that, either JHDL.jar, axis2-adb-1.2.jar and derby.jar are in the same directory as fss.jar, or symbolic links exist there. An alternative is to put the absolute path of each JAR file in the command.)
Here, the Java application launcher has been given two command-line options and the name of the class to be invoked. The first command-line option, -d64 specifies that the program is to be run in a 64-bit environment. The -d64 option may only be used on 64-bit systems. The second command-line option, -cp fss.jar:JHDL.jar:axis2-adb-1.2.jar:derby.jar specifies a list of JAR archives to search for class files. The name of the class to be invoked is com.alanfeldstein.sparc.fss.SparcCaseStudy. The ampersand (&) causes asynchronous execution of the preceding pipeline, that is, the shell does not wait for that pipeline to finish. The authoritative source about parameters is the documentation for your Java application launcher.
If FSS does not have access to a test cases database, then you will see a nonfatal exception about that in the shell. However, interactive verification is still possible. To enable automated verification, see Specification for Providing a Test Cases Database. After performing automated verification with the simulator application, there is a postsimulation application in the FSS application suite that allows you to view the results database. For example:
$ cd /opt/fss $ java -d64 -cp postsimulation.jar:table.jar:derby.jar -Dderby.system.home=$HOME/derby com.alanfeldstein.sparc.postsimulation.DisplayAutomatedVerificationResults &
Interactive verification requires that you use the "Load 1 Program" button to load from an ELF file into simulated memory.