Hi to all in this discussion,
I wanted to add some points to the discussion above regarding ARM+ RUBY. I
have been working with ARM +RUBY and I have simulated 2x2/ 4x4 Mesh_XY NoC
with MESI_Two_Level protocol. This protocol works fine with ARM in full
system mode. But originally MESI_Two_Level
Hi Paul,
It's in my brain, why don't other know this automatically ;).
ARM works well with all of the CPU models and the classic caches. There are
limited cases where ARM works with Ruby. To find out what ARM+Ruby is
supported I would look back through the commit log to see which protocols
have
Hi Jason,
Hmm, do you have a sense for which (just a small subset is fine)
combinations are a good idea to run and/or which aren't :-).
Paul
On Fri, Feb 23, 2018 at 5:09 PM, Jason Lowe-Power
wrote:
> Hi Paul,
>
> Yeah, the status matrix is very out of date. I would like to
Hi Paul,
Yeah, the status matrix is very out of date. I would like to see it
automatically updated by our regression tests / continuous integration
tests. However, those are also wildly out of date.
It would be *fabulous* if someone had time / money / energy to revamp our
testing infrastructure
Hey Jason,
Sure no problem, my guess is that the uninitialized warning/error is ARM
specific (its in some neon memory file) so maybe that's why it fell
through? BTW, on a similar note, I see that the gem5 status matrix (
http://gem5.org/Status_Matrix) hasn't been updated in a number of years, is
Thanks Ciro! yeah I saw that patch right after I posted. Haven't tried it
out yet though as I got it to work by adding those two hacks to the
SConfigure file. I'd probably prefer not to do the gcc rollback since part
of what I'm doing is getting this up and running for some lab assignments I
Hi Paul,
Thanks for letting us know. There's currently a patch on our review site
that solves the implicit fallthrough problem (
https://gem5-review.googlesource.com/c/public/gem5/+/8541). I haven't seen
the uninitialized warning, though.
Cheers,
Jason
---
Jason Lowe-Power
Assistant
I reproduce.
There was already a patch to port to 7.2.0 at
5c41076bd7610d03431fd0dd89bd0fdc7f30d6bd but the migration wasn't complete.
One workaround that does not require modifying the code is:
sudo apt-get install g++-6 gcc-6
CC=gcc-6 CXX=g++-6 scons