ok dokie.... running tests now, will post temporary fix soon...

On Thu, Jul 7, 2011 at 8:20 PM, Gabriel Michael Black <[email protected]
> wrote:

> Yes, please.
>
> Gabe
>
>
> Quoting Ali Saidi <[email protected]>:
>
>  We can debate the fix whenever, but at the moment the issue remains that
>> the head of the tree is broken. If it's a simple fix, then please fix and
>> lets be done with it, but if it's going to take any time please undo your
>> changes so that the tree can be working again.
>>
>> Thanks,
>> Ali
>>
>>
>> On Thu, 7 Jul 2011 16:12:49 -0400, Korey Sewell <[email protected]>
>> wrote:
>>
>>> Nope,
>>> I was going to put O3 back to the old way and then the workaround in
>>> inorder.
>>>
>>> This problem all centers around marking the hwrei instruction w/the
>>> isControl flag.
>>>
>>> On Thu, Jul 7, 2011 at 3:38 PM, nathan binkert <[email protected]> wrote:
>>>
>>>  I don't want to make this more complicated than necessary, but did you
>>>>>> figure out why flagging hwrei as "isControl" breaks O3?
>>>>>>
>>>>>
>>>>> Nope, I just never got the sit-down time to figure out this solution so
>>>>> I
>>>>> was going to temporarily "unControl" hwrei so the other people could
>>>>> work
>>>>> until I get the bandwidth to fix this the "right way" (or at the very
>>>>>
>>>> least
>>>>
>>>>> a convoluted way)
>>>>>
>>>>
>>>> I'm barely following the thread, but just to confirm, your going to
>>>> put the workaround into O3, right?  If O3 is "broken" I think the
>>>> workaround should be in O3.  It seems wrong to me to do the dynamic
>>>> thing in inorder if it is correct.
>>>>
>>>> Nate
>>>> ______________________________**_________________
>>>> gem5-dev mailing list
>>>> [email protected]
>>>> http://m5sim.org/mailman/**listinfo/gem5-dev<http://m5sim.org/mailman/listinfo/gem5-dev>
>>>>
>>>>
>> ______________________________**_________________
>> gem5-dev mailing list
>> [email protected]
>> http://m5sim.org/mailman/**listinfo/gem5-dev<http://m5sim.org/mailman/listinfo/gem5-dev>
>>
>>
>
> ______________________________**_________________
> gem5-dev mailing list
> [email protected]
> http://m5sim.org/mailman/**listinfo/gem5-dev<http://m5sim.org/mailman/listinfo/gem5-dev>
>



-- 
- Korey
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev

Reply via email to