* build/RISCV/tests/opt/quick/se/02.insttest/riscv/linux-rv64c/o3-timing:
FAILED!
*
build/RISCV/tests/opt/quick/se/02.insttest/riscv/linux-rv64c/simple-timing-ruby:
FAILED!
*
build/RISCV/tests/opt/quick/se/02.insttest/riscv/linux-rv64c/simple-atomic:
FAILED!
*
build/RISCV/test
Hello Andreas Sandberg,
I'd like you to do a code review. Please visit
https://gem5-review.googlesource.com/10101
to review the following change.
Change subject: cpu: Avoid unnecessary dynamic_pointer_cast in atomic model
...
Hello Curtis Dunham,
I'd like you to do a code review. Please visit
https://gem5-review.googlesource.com/10102
to review the following change.
Change subject: mem: Optimize self-refresh entry
..
mem: Optimize self-refres
Hello Nikos Nikoleris,
I'd like you to do a code review. Please visit
https://gem5-review.googlesource.com/10103
to review the following change.
Change subject: mem: Add support for more flexible DRAM timing and
topologies
...
Jason Lowe-Power has submitted this change and it was merged. (
https://gem5-review.googlesource.com/9981 )
Change subject: docs: Fix power model doxygen
..
docs: Fix power model doxygen
Change-Id: I0a9a30bc4a89411e0f1dd897f0
Jason Lowe-Power has uploaded this change for review. (
https://gem5-review.googlesource.com/10121
Change subject: tests: Add explicit build test
..
tests: Add explicit build test
Change-Id: Ia613ab580b880a463c9cf0dd63f61497
Jason Lowe-Power has uploaded a new patch set (#10) to the change
originally created by Sean Wilson. (
https://gem5-review.googlesource.com/4423 )
Change subject: tests: Add test for the m5-exit instruction.
..
tests: Add te
Jason Lowe-Power has uploaded a new patch set (#10) to the change
originally created by Sean Wilson. (
https://gem5-review.googlesource.com/4421 )
Change subject: tests,ext: Add a new testing library proposal
..
tests,ext: A
Hello Sean Wilson, Gabe Black,
I'd like you to reexamine a change. Please visit
https://gem5-review.googlesource.com/4882
to look at the new patch set (#10).
Change subject: tests: Add documentation for new testing code
..
Hi Alec,
What you're describing is *hard* and requires a lot of coordination between
people. I think the best way to do it today is to use something out-of-band
like a github mirror and then have one person rebase, etc. and submit to
the mainline. That's basically what AMD and ARM do internally. I
10 matches
Mail list logo