Yeah, that's what I was asking. Sounds a lot easier than what I was
thinking I would have to do, too. Thanks!
On Mon, Apr 23, 2018 at 12:54 PM, Jason Lowe-Power
wrote:
> Hi Alec,
>
> On github you should be using a different branch other than master (say,
> riscv-fs).
Hello Tuan Ta, Robert Scheffel,
I'd like you to reexamine a change. Please visit
https://gem5-review.googlesource.com/7441
to look at the new patch set (#5).
Change subject: arch-riscv: Update CSR implementations
..
Hi Ciro (and Gabe),
We're working on this... it's just slow. We're weighing our options for how
to manage hosting and hosting providers. This is just something that's
going to take time :).
Cheers,
Jason
On Sun, Apr 22, 2018 at 2:28 PM Ciro Santilli wrote:
> Who would
Hi Alec,
On github you should be using a different branch other than master (say,
riscv-fs). Then, you can just rebase that branch on top of master (or
origin/master if you've got other commits on master). I often use "git
rebase -i master" when doing this. Then, during the rebase you can
Hello Gabe Black, Anthony Gutierrez, Jason Lowe-Power, Nikos Nikoleris,
Andreas Sandberg, Brandon Potter,
I'd like you to reexamine a change. Please visit
https://gem5-review.googlesource.com/9781
to look at the new patch set (#2).
Change subject: sim,cpu,mem,arch: Introduced MasterInfo
*** stat_diff: FAILURE: Statistics mismatch*
build/RISCV/tests/opt/quick/se/02.insttest/riscv/linux-rv64c/minor-timing:
FAILED!
*** diff[config.json]: SKIPPED*
build/RISCV/tests/opt/quick/se/02.insttest/riscv/linux-rv64c/o3-timing: FAILED!
*