PS: This issue was fixed about two weeks ago by putting in an assert to
warn when MaxWidth was <= any width in the machine.  So it's in the
mainline, just not in gem5-stable.

http://repo.gem5.org/gem5?cmd=changeset;node=790a214be1f4


On Tue, May 13, 2014 at 4:36 PM, Mitch Hayenga <mitch.hayenga+g...@gmail.com
> wrote:

> Gem5 has some hard compile-time limits on how large certain widths can be.
>  In src/cpu/o3/impl.hh there is a line that sets "MaxWidth = 8".  Increase
> this to greater than or equal to 16 (or whatever the maximum width in your
> machine is).
>
> The issue you are hitting is time buffer entries writing into invalid
> memory because of this compile time limit.
>
>
> On Tue, May 13, 2014 at 4:29 PM, Jordan Fix via gem5-users <
> gem5-users@gem5.org> wrote:
>
>> Hello,
>>
>> I believe I have found a bug in the O3 cpu model. I have simply adjusted
>> the renameWidth from 8 to 16 in src/cpu/o3/O3CPU.py. Doing this causes the
>> commit unit to seg fault at line 1286 in src/cpu/o3/commit_impl.hh.
>>
>> It appears the fromRename buffer size is incorrect (value of 55356032).
>> This is causing the loop to access invalid locations in the fromRename
>> buffer.
>>
>> This is with the latest gem5-stable.
>>
>> command line: build/ALPHA/gem5.debug configs/example/se.py
>> --cpu-type=detailed --caches -c $BENCHMARK
>>
>> Thanks,
>> Jordan
>>
>>
>> _______________________________________________
>> gem5-users mailing list
>> gem5-users@gem5.org
>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>>
>
>
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to