saterus / asm_simulator Goto Github PK

I think we need that don't we?

• Explain how to download the Java runtime.
• Explain how to unzip a zip file.
• Explain how to install Eclipse.
• Shoot yourself.

my test case for Junit seems to be correct, unless im doing it wrong...

public final void STTest()
{
short fin;
m.setMemory((short) (m.getPCRegister().getValue() & 0xfe00 | (short)8), (short)4);
m.getRegister(r0).setValue((short) 1);
final ST st=new ST(r0,8);
st.execute(m);

    fin=m.getMemory((short) (m.getRegister(r0).getValue()));
    assertEquals("equals",(short)4,fin);

}

if you guys go to Lab 2 handout sheet on assembler. If you look at the sample code, they listed JMP and JMPR instruction, which aren't part of the MMXI specification. So I'm assuming the professor wanted the program to be able to read JMP and JMPR as JSR and JSRR?

They said they wanted a JUNIT table, can't we just print out the source code of our Junit tests?

I am trying to use Utilities.parseShort() for parsing .ORIG 0xFFFF and i get an error. Looking into it now.

i added, LD, LDI, LDR, NOT and RET test cases last night, i dunno if you saw the updates, but you made some more similar test cases of the same intstructions.. oh well, more testing the better.

CODE:
final TRAP trap = new TRAP(0x33);
trap.execute(m); //errors here

java.lang.StringIndexOutOfBoundsException: String index out of range: 2
at java.lang.String.substring(Unknown Source)
at edu.osu.cse.mmxi.ui.UI.getShort(UI.java:87)
at edu.osu.cse.mmxi.machine.interpreter.instructions.Instruction$TRAP.execute(Instruction.java:633)
at edu.osu.cse.mmxi.junit.ManualJUnitTest.trapx33goodValEnter9(ManualJUnitTest.java:91)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)

I beleive the unit tests are correct in LEA not working.

Should be:
registerX = getMemAt(PC+offset)

Can someone familiar with the current state of the UI package detail its contents in the Programmer's Guide? I'm not up to speed with it anymore.

There was an issue with ADDimm. Will fix.

Table of JUnit descriptions.

Currently, it just keeps going.

Does not print message on multiple modes being given. Only 1 should be allowed. I reviewed this and am not certain why this is happening.

If you look at the common parser

public static void errorOnUndefinedSymbols(final Set undef) function,

it throws the P2_INST_BAD_SYMBOL error code. But it's not in the ASMcode section.

I do not believe step mode works properly.

Documents say:

Print a prompt on the screen and read a decimal number from the keyboard.
The number is echoed to the screen and stored in R0. You may place speci c
requirements on the size, formatting, etc. of the input

We currently do not echo the value back to screen.

We should make sure the User Guide and Dev Guide have the same basic Style and Formatting, for consistency's sake.

check out the src.edu.osu.cse.mmxi.junit.InstructionTest

run the test serveral times and you will see AndTrueTrue2ImmTest() Fails sometimes. Havent looked into it much.

Cite the image, and put it near the documentation.