On 2013-04-30 13:00, Andreas Färber wrote:
Not sure if you understood my point? Exposing cpu_env from target-arm would seem to torpedo our efforts to link target-arm and, e.g., target-microblaze together, since they all have cpu_env. I don't really care if it's qom/cpu.c or tcg/shared.c or renaming to arm_cpu_env. :)
cpu_env is still static within target-microblaze/translate.c; there is no conflict ... yet. r~
