Hi ARM gem5 folks. I've been trying to develop some tests for the various
forms of calling gem5 ops, and am trying to run them on QEMU as an easy way
to (approximately) run them on other architectures. I've run into a few
problems which I've been discussing with the QEMU folks, and outside of a
few small shortcomings of QEMU, one problem that they pointed out that our
implementation has is that form 32 bit ARM we're using accesses to a
coprocessor which isn't supposed to exist as our pseudo instructions.

That kind of works, except that that coprocessor may actually exist, and it
does exist in the QEMU implementation to support very old ARM binaries.
Changing to some other instructions at this point would be very difficult,
but I'm slightly concerned that the instructions we picked aren't
necessarily actually unused, outside of the difficulty that causes with
QEMU.

Do any ARM folks have an opinion on what we should do here? Is 32 bit ARM
out of the mainstream enough where we could change it and not cause
everyone huge headaches? I think we can keep the hooks for it in its
current location but move the official instructions somewhere new, if we
wanted.

Gabe
_______________________________________________
gem5-dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

Reply via email to