Move away from UAE/dyngen code

[MaddTheSane]

As Clang has issues with global register variables, perhaps moving to a different emulation system would be welcome. The first thing to come to mind is Qemu's TCG and TCI. As the current TCG uses a global register variable right now, the TCI back-end would be the best bet to work with Clang. Another course of action is to check if the compiler supports global register variables and use TCI if it doesn't and the proper processor back-end if it does.

Correct me if I'm wrong, but the dyngen code came from Qemu, right?

[MaddTheSane]

Some news on the Qemu front: you don't need to use the TCI when compiling with Clang: just a vanilla build works fine.

[asvitkine]

The dyngen step is used to generate some (architecture-specific) C++ code that then gets compiled as part of the regular build.

We could check in these generated sources for various platforms, which could then be used with clang (since it's only generating them that doesn't work with clang).

We'd need to modify the various build files to support that and to check in the generated files for the different platforms.

[morgant]

@MaddTheSane @asvitkine has started addressing this as mentioned above as part of the discussion in Issue #98.