---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/1664/#review3897
---
I think the need for this somewhat depends on the threading model. It see
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/1664/
---
Review request for Default.
Description
---
Changeset 9480:c1585edc3d31
--
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/1662/#review3896
---
Ship it!
Ship It!
- Anthony Gutierrez
On Jan. 22, 2013, 1:50 p.m., Al
Thanks for getting this done Nilay.
Ali
On 24.01.2013 12:25,
Nilay Vaish wrote:
> changeset d059f8a95a42 in /z/repo/gem5
> details:
http://repo.gem5.org/gem5?cmd=changeset;node=d059f8a95a42 [1]
>
description:
> branch predictor: move out of o3 and inorder cpus
> This
patch moves the branch
changeset b0fa6b872f40 in /z/repo/gem5
details: http://repo.gem5.org/gem5?cmd=changeset;node=b0fa6b872f40
description:
regressions: update stats due to branch predictor changes
The actual statistical values are being updated for only two tests
belonging
to sparc architectur
changeset d059f8a95a42 in /z/repo/gem5
details: http://repo.gem5.org/gem5?cmd=changeset;node=d059f8a95a42
description:
branch predictor: move out of o3 and inorder cpus
This patch moves the branch predictor files in the o3 and inorder
directories
to src/cpu/pred. This allow
I think the parser issues we've had before and it even depends on how it
is executed on zizzer (on command line, through python, and even with
different ways of invoking it through python)
Andreas
On 24/01/2013 18:17, "Nilay" wrote:
>On Thu, January 24, 2013 8:50 am, Nilay wrote:
>> On Thu, Jan
On Thu, January 24, 2013 8:50 am, Nilay wrote:
> On Thu, January 24, 2013 3:08 am, Nilay wrote:
>
>>
>> Seems like I will not be able to keep my promise. Following differences
>> were found after running all the regression tests --
>>
>> 1. tests/long/se/20.parser/ref/arm/linux/o3-timing/
>> sim_
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/1660/#review3895
---
What's the point of the avoidQuiesceLiveLock flag? Is there anything prev
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/1471/#review3894
---
Ship it!
Ship It!
- Andreas Sandberg
On Jan. 23, 2013, 11:37 a.m., An
On Thu, January 24, 2013 3:08 am, Nilay wrote:
>
> Seems like I will not be able to keep my promise. Following differences
> were found after running all the regression tests --
>
> 1. tests/long/se/20.parser/ref/arm/linux/o3-timing/
> sim_insts 505237723 505237723
On Tue, January 15, 2013 6:15 pm, Ali Saidi wrote:
>
> On Jan 15, 2013, at 6:59 PM, Nilay Vaish wrote:
>
>> On Tue, 15 Jan 2013, Ali Saidi wrote:
>>
>>>
>>>
On Jan. 8, 2013, 6:29 a.m., Ali Saidi wrote:
> Hi Nilay,
>
> Thanks for resurrecting this. In principle I have no issues, I
scons: `build/ALPHA/gem5.debug' is up to date.
scons: `build/ALPHA_MOESI_hammer/gem5.debug' is up to date.
scons: `build/ALPHA_MESI_CMP_directory/gem5.debug' is up to date.
scons: `build/ALPHA_MOESI_CMP_directory/gem5.debug' is up to date.
scons: `build/ALPHA_MOESI_CMP_token/gem5.debug' is up to da
13 matches
Mail list logo