- I think master should be stable
- I think gem5 should be released three times per year
Regards,Daniel
Em segunda-feira, 16 de dezembro de 2019 22:33:14 GMT+1, Bobby Bruce
escreveu:
* I think master should be stable
* I think gem5 should be released three times per year
--
Dr.
* I think master should be stable
* I think gem5 should be released three times per year
--
Dr. Bobby R. Bruce
Room 2235,
Kemper Hall, UC Davis
Davis,
CA, 95616
On Mon, Dec 16, 2019 at 11:50 AM Jason Lowe-Power
wrote:
> Hi all,
>
> As many of you have seen on gem5-dev, we are going to be
Hi Jason,
"I think master should be stable"as common case should be to use gem5 and
not to dev it.
"I think gem5 should be released three times per year." as I assume there
would be too much to digest after one year.
Best,
On Mon, Dec 16, 2019 at 12:21 PM Tao Zhang wrote:
> Hi Jason,
>
>
Hi Jason,
Thanks for the proposal.
Regarding the branch option for stable release, can we do it by git tagging?
I think one-release per year is too long. I prefer three-release per year.
Thanks,
-Tao
On Mon, Dec 16, 2019 at 11:50 AM Jason Lowe-Power
wrote:
> Hi all,
>
> As many of you
- "I think master should be stable"
- "I think gem5 should be released three times per year."
Matt
On Mon, Dec 16, 2019 at 1:57 PM Abhishek Singh <
abhishek.singh199...@gmail.com> wrote:
> Hello Jason,
> Thanks for such a nice and detailed explanation.
> My votes are as follows:
>
>
> *I think
Hello Jason,
Thanks for such a nice and detailed explanation.
My votes are as follows:
*I think master should be development*
*I think gem5 should be released once per year*
Best regards,
Abhishek
On Mon, Dec 16, 2019 at 2:50 PM Jason Lowe-Power
wrote:
> Hi all,
>
> As many of you have
Hi all,
As many of you have seen on gem5-dev, we are going to be adding a
"stable" version of gem5. Below is the current proposal. There are a
couple of points below where there has not been general consensus
reached. We would appreciate feedback *from everyone in the community*
on the points
Hi,
Very interesting observation. There are several explanations here. First,
you may want to look at branch mispredictions. The pipeline flushes due to
memory order violations may be shadowed by flushes due to branch
mispredictions. You may want to increase your LSQ size to allow more
inflight
