[gem5-dev] Change in public/gem5[master]: mem-ruby: Support atomic_noncaching acceses in ruby

Swapnil Haria has submitted this change and it was merged. ( https://gem5-review.googlesource.com/5601 ) Change subject: mem-ruby: Support atomic_noncaching acceses in ruby .. mem-ruby: Support atomic_noncaching acceses in rub

[gem5-dev] Change in public/gem5[master]: arch-riscv: Define AT_RANDOM properly

Alec Roelke has submitted this change and it was merged. ( https://gem5-review.googlesource.com/6681 ) Change subject: arch-riscv: Define AT_RANDOM properly .. arch-riscv: Define AT_RANDOM properly According to the getauxval(

[gem5-dev] Change in public/gem5[master]: arch-riscv: Define AT_RANDOM properly

Alec Roelke has uploaded a new patch set (#2). ( https://gem5-review.googlesource.com/6681 ) Change subject: arch-riscv: Define AT_RANDOM properly .. arch-riscv: Define AT_RANDOM properly According to the getauxval(3) man pag

Re: [gem5-dev] Using branching in gem5 public

Hi Tony, I'm generally all for using branches, we use them extensively internally. IMO, the options we have in gerrit for what both of us are trying to accomplish, us with SVE and you with the GPU, are as follows: 1. We create different repositories per user / institution and push between repos.

Re: [gem5-dev] Using branching in gem5 public

Hey Tony, A few thoughts: I think it's a good idea to post pre-production code publicly. This gives other developers a chance to see and comment on the design (well, it *could*), and, more importantly, it gives users access to new features quickly. There is one potential downside to the above: L

[gem5-dev] Change in public/gem5[master]: arch-riscv: Define AT_RANDOM properly

Alec Roelke has uploaded this change for review. ( https://gem5-review.googlesource.com/6681 Change subject: arch-riscv: Define AT_RANDOM properly .. arch-riscv: Define AT_RANDOM properly According to the getauxval(3) man pa

[gem5-dev] Using branching in gem5 public

Hi All, I have a question about using branches in the mainline gem5 repo. I see ARM have a separate repo here: https://gem5-review.googlesource.com/admin/projects/arm/gem5. It is used for staging ARM features under development. At AMD we would like to do something similar, as we have some sign

[gem5-dev] Change in public/gem5[master]: arch-riscv: Increase maximum stack size

Alec Roelke has submitted this change and it was merged. ( https://gem5-review.googlesource.com/6661 ) Change subject: arch-riscv: Increase maximum stack size .. arch-riscv: Increase maximum stack size This patch increases th

[gem5-dev] Cron /z/m5/regression/do-regression quick

* build/RISCV/tests/opt/quick/se/02.insttest/riscv/linux-rv64m/minor-timing: FAILED! * build/RISCV/tests/opt/quick/se/02.insttest/riscv/linux-rv64f/simple-atomic: FAILED! * build/RISCV/tests/opt/quick/se/02.insttest/riscv/linux-rv64m/simple-atomic: FAILED! * build/RISCV/tests