Include a successful output file

[JJAYL]

It might be helpful for some people to compare your non segfaulting CPU output with theirs (like a counterpart the current example-output.txt)

[0x647262]

Adding to this, a buildloop can fail because of issues unrelated to segfaulting.

In file included from /mnt/ramdisk/workdir/gcc-7.1.0/libgcc/unwind-dw2.c:403:0:
./md-unwind-support.h: In function 'x86_64_fallback_frame_state':
./md-unwind-support.h:65:47: error: dereferencing pointer to incomplete type 'struct ucontext'
       sc = (struct sigcontext *) (void *) &uc_->uc_mcontext;
                                               ^~
make[3]: *** [/mnt/ramdisk/workdir/gcc-7.1.0/libgcc/shared-object.mk:14: unwind-dw2.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory '/mnt/ramdisk/workdir/buildloop.d/loop-3/x86_64-pc-linux-gnu/libgcc'
make[2]: *** [Makefile:21950: all-stage1-target-libgcc] Error 2
make[2]: Leaving directory '/mnt/ramdisk/workdir/buildloop.d/loop-3'
make[1]: *** [Makefile:27079: stage1-bubble] Error 2
make[1]: Leaving directory '/mnt/ramdisk/workdir/buildloop.d/loop-3'
make: *** [Makefile:942: all] Error 2

~I'll open a PR for this when I have some time.~ Nevermind, I see this repository is frozen.

[suaefar]

Yes, the issue is known. Remember that this script does not calculate anything deterministic. It is likely to trigger a hardware bug under certain conditions (Ubuntu 17.04!). I cant change it without risking that it looses this property.

Yes, I can add the output of a sucessful run.

[0x647262]

Thanks a bunch! :)