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 and get some of these things up to date. There was
some work last summer in re-writing the regression tester that was never
finished, Gabe has done some great work getting the unittests working
again, and I know that internally AMD and ARM have tests that run. It's
unfortunate that it's not a priority for me :/. This is what I feel most
guilty about ;).
If you know of anyone (junior grad students, masters students, motivated
undergrads, anyone who wants to contribute to an open source project, etc.)
who would be up for working on this, I'm happy to help advise! This isn't a
*hard* project. It will just take some time and effort. This would have
very significant impact on this project. I can't think of anything that
would have a broader impact!
On Fri, Feb 23, 2018 at 4:15 AM Paul V. Gratz <pgr...@gratz1.com> wrote:
> 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 that matrix still valid? If not is there a good source for that kind of
> info (or have the various combos become generally more supported?).
> How is your first year at UCD going! Are you going to be at HPCA this
> year? Incidentally, I ran across your learning gem5 site and have been
> working through it, thanks for that site, its great!
> On Thu, Feb 22, 2018 at 4:16 PM, Jason Lowe-Power <ja...@lowepower.com>
>> 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.
>> Jason Lowe-Power
>> Assistant Professor, Computer Science Department
>> University of California, Davis
>> 3049 Kemper Hall
>> On Thu, Feb 22, 2018 at 5:56 AM Paul V. Gratz <pgr...@gratz1.com> wrote:
>>> Hi All,
>>> I just did a clean clone of the latest github on my Ubuntu 17.10 system
>>> (gcc 7.2.0). In this setup builds fail due to two warnings (because
>>> -Werror is on in the build scripts).
>>> First in decode-method.cc.inc there are some case statements that have
>>> fallthrough conditions. To get around this I added:
>>> to the SConstruct file (is this the right way to do this?).
>>> Second, in neon64_mem.hh there are some potentially uninitialized
>>> variables. To get around this I added maybe-uninitialized to the CCFLAGS:
>>> After this the build completes cleanly. Probably those warnings should
>>> be fixed in the source code directly but I am not yet well versed enough in
>>> how gem5 works to do that yet. I'm guessing that these warnings are new
>>> with my gcc version is why I don't see anyone posting on here about them
>>> Paul V. Gratz
>>> Associate Professor
>>> ECE Dept, Texas A&M University
>>> Office: 333M WERC
>>> Phone: 979-488-4551 <(979)%20488-4551>
>>> gem5-users mailing list
>> gem5-users mailing list
> Paul V. Gratz
> Associate Professor
> ECE Dept, Texas A&M University
> Office: 333M WERC
> Phone: 979-488-4551 <(979)%20488-4551>
> gem5-users mailing list
gem5-users mailing list