, and will it be
accessible to the public?
-Tony
-Original Message-
From: gem5-dev [mailto:gem5-dev-boun...@gem5.org] On Behalf Of Andreas Hansson
Sent: Monday, November 14, 2016 2:40 PM
To: gem5 Developer List <gem5-dev@gem5.org>; Jason Lowe-Power
<ja...@lowepower.com>
Subject: Re: [gem5-dev] Stat
Hi Andreas,
I don't think it's surprising, but I like this idea. I think it's much more
maintainable going forward than what we've been doing.
Does this have any bearing on the RISC-V patches? I was hoping we would be
able to get Alec's stuff pushed in soon. I don't want to hold things up for
Hi all,
Merely a thought when it comes to adding tests:
I would suggest we ditch all proprietary/closed-source tests and move in
the direction of something that is open and maintained. My proposal would
be to adopt a few of the tests from the llvm test suite. There are both
very short
I think I get it. Thanks for your help!
It looks like I won't be able to make use of any tests other than 00.hello,
because either they're multithreaded or pieces of them are missing. I'm
going to try to put my instruction tests into 02.insttest.
On Fri, Oct 28, 2016 at 11:01 AM, Jason
Hi Alec,
Our regression testing infrastructure is confusing, to say the least.
Honestly, it would take me at least a few hours to figure out how to add
new regressions again. But here's a little information that hopefully will
help you save some time.
You need to put reference outputs in
I'll start with converting as many from "quick" as I can. If/when I end up
creating my own, is there a convention for what they should be named and
where they should go?
Also, I'm having a bit of a problem with just 00.hello. I compiled the
source in tests/test-progs/hello/src into
I'll certainly add regressions for "hello" for each of the four models, and
I'll try to get other "quick" tests done the same way, too. I won't be
able to do all of them as m5threads hasn't been implemented for RISC-V, but
I'll do what I can. I can also do the "long" ones the same way, if time
Hi Alec,
Thanks for taking the time for writing tests. It's something that we as a
community need to get better at.
To respond to your questions:
- It is completely acceptable for you to include RISC-V only tests. In
fact, I think it's a necessity.
- Focusing just on the "quick" regressions
Hi Alec,
Thanks again for implementing RISC-V in gem5. It's an incredibly important
and timely addition!
As far as I can tell, the patches look good. Hopefully some other will
review them soon as well.
The only thing that's missing that I would really like to have before
pushing the patches is
