Bobby,
You suggestion (number 3) worked, and I was able to run the compiled gem5.opt
by fixing generator=generator. I did have an additional error which I corrected
by:
motherboard._pre_instantiate()
m5.instantiate()
I am including the two runs (with error and no error). I have a couple of
co
I think there are a few things going on here causing problems.
1. The pre-commit hooks aren't being installed correctly. i think this is due
to some directory permission error. The '/.cache' directory appears to not have
the right permissions here. Perhaps this you did something here with sudo?
There's a lot of information missing in your email, but I'll make some
guesses and try to help.
If you're using x86 and you compiled lbm on your host, then most likely it
is using SSE/AVX/vector instructions that may not be implemented or
implemented incorrectly in gem5. I would expect to see warn
Hi Nick,
You should be able to `cd` to the gem5 directory, set up a remote to the
new github location (`git remote add upstream https://github.com/gem5/gem5`)
then checkout stable (`git checkout upstream/stable`). (Note: commands off
the top of my head and may have mistakes.)
That said, be carefu
Hello,
You can use the special "m5ops" instructions to communicate between your
workload and the simulator. The documentation is here:
https://www.gem5.org/documentation/general_docs/m5ops/
The available instructions are listed here, and you can build these wrapper
functions into a library to l
