Both sound fine to me.

Steve

On Mon, Apr 27, 2015 at 1:30 AM, Andreas Hansson <[email protected]>
wrote:

> Hi all,
>
> With the recent removal of the old InOrderCPU, I’d suggest we proceed and
> rename MinorCPU to InOrderCPU. This will mark the final step in the
> transition. Let me know if you disagree or think it is too early.
>
> A follow-on issue is that the status matrix is horribly out of date, and I
> suggest as part of this name change we update and simplify the matrix. To
> make things easier I’d suggest to break out the Ruby coherence protocols,
> and have a single column for Ruby on the overall status page, and then a
> second page with all the gory details.
>
> In short, do you agree/disagree with the following:
>
> 1. Renaming MinorCPU to InOrderCPU
>
> 2. Update and split the status matrix to have a single Ruby column
>
> Thanks,
>
> Andreas
>
>
> -- IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
>
> ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ,
> Registered in England & Wales, Company No: 2557590
> ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ,
> Registered in England & Wales, Company No: 2548782
> _______________________________________________
> gem5-dev mailing list
> [email protected]
> http://m5sim.org/mailman/listinfo/gem5-dev
>
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev

Reply via email to