`self-assembler` assignment results in timeout about selfie HOT 7 CLOSED

It seems like both assembling and disassembling takes significantly longer on mipster than just compilation.
Maybe we could:

1. Compile, disassemble, assemble, and store a selfie binary
2. Load the binary into a mipster instance and let it compile and store a selfie binary.
3. Compare the resulting binaries from step 1 and 2

If the assemble step is working correctly, the binary from step 1 should be logically equivalent to the host's selfie and produce the same binary in step 2.

from selfie.

@Blazefrost Sounds good! Please do a PR.

from selfie.

Thoughts about that, @ckirsch @Blazefrost ?

from selfie.

How would you change the test?

from selfie.

Maybe compile selfie once from the C* source and assemble it from the output generated by -s and then compare the resulting binaries.

from selfie.

I thought that is what self-assembler checks...what does it actually check?

from selfie.

See for yourself:

    return check_execution('./selfie -c selfie.c -s selfie1.s -a selfie1.s -m 128 -a selfie1.s -s selfie2.s ',
                           'selfie can assemble its own binary file') + \
        check_execution('diff -q selfie1.s selfie2.s',
                        'both assembly files are exactly the same')

from selfie.