> Brad
>
>
> -Original Message-
> From: gem5-dev [mailto:gem5-dev-boun...@gem5.org] On Behalf Of Andreas Hansson
> Sent: Tuesday, April 12, 2016 3:08 PM
> To: gem5 Developer List <gem5-dev@gem5.org>
> Subject: Re: [gem5-dev] Memory consistency verification (and
Hi Andreas,
Thanks for the comments. I hope pruning ext/ (McPat?) is not a
pre-requisite for getting my library in.
Regarding MemChecker: I can imagine that it keeps accumulating and
allocating more and more addresses over time, the longer the system is
running.
McVerSi is very different from
regression tests rely on
code in the ext/ directory.
Thanks,
Brad
-Original Message-
From: gem5-dev [mailto:gem5-dev-boun...@gem5.org] On Behalf Of Andreas Hansson
Sent: Tuesday, April 12, 2016 3:08 PM
To: gem5 Developer List <gem5-dev@gem5.org>
Subject: Re: [gem5-dev] Memory consi
Hi Marco,
This sounds good.
Regarding the external component, I certainly do not mind. I would suggest
we prune the old and crufty McPat. That should free up some 45k LoC, and I
there is not really any integration in place in any case.
Do you also have any updates to the MemChecker? It is
Hi all,
I've been working on integrating McVerSi [1] (a framework for
simulation-based memory consistency verification) into the latest Gem5
version; in doing so I have also discovered new bugs (see end of email).
At [1] I provide a patch and instructions on how to use McVerSi with the
current
