I have no plans to attend HPCA at the moment.
There are folks here who are using my original version of this patch and
would like to check it into our internal version of gem5, but I think we
should use a version of it that doesn't break anything else in the process.
Unfortunately I don't have an
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/3378/#review9357
---
Ship it!
Ship It!
- Pierre-Yves Péneau
On Jan. 31, 2017, 2:44 p.m.,
> On Jan. 30, 2017, 10:31 p.m., Gabe Black wrote:
> > Hi folks. I put together this patch a long time ago, there was some
> > discussion about it, and then I lost track of what was going on with it.
> > Have the issues it causes with AMD cpus been tracked down? Glancing through
> > this
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/3798/#review9355
---
I don't follow why you don't need to pay for the payload delay. Is that
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/3797/#review9354
---
Ship it!
Ship It!
- Jason Lowe-Power
On Jan. 30, 2017, 4:38 p.m.,
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/3378/#review9352
---
Ship it!
Ship It!
- Jason Lowe-Power
On Jan. 31, 2017, 1:44 p.m.,
Dear all,
I updated some of the patches (mostly spell fixes) and add a fee new patches to
the series [1-4]. Most notably, [1] ensures correct handling of gem5 packets
when two gem5 components communicate with each other over a SystemC
interconnect. [2] is a small bugfix and [4] a small
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/3799/
---
Review request for Default.
Repository: gem5
Description
---
Changeset