Ah, ok, immediately after I sent this I happened to find a paragraph that
said if you try to kill your parent and all their descendants, you'll get
to yourself and stop. I'm not sure if that's intended or "intended" (ie
that's what it did so that's in the spec), but at least that clarifies
things.
Hi systemc gurus. I have a question about systemc processes throwing
exceptions at each other, including the sc_unwind_exception when calling
kill() or reset() on a process handle.
What *should* happen when you call, for instance, kill() on your parent
process and tell it to include descendants? A
That binary is for HSAIL, so it will not run for GCN3. The model currently only
supports GCN3 ISA binaries and host apps which use the ROCm stack.
The config issue is due to this change:
https://gem5.googlesource.com/amd/gem5/+/a0d42e05f700048b3a77d673ca992e227ac982e0,
which changed those param
Hi Tony and Tuan,
I have cloned the agutierr/master-gcn3-staging branch of gem5 available on
"https://gem5.googlesource.com/amd/gem5/"; and have built GCN3_X86/gem5.opt
using the default GCN3_X86 file in build_opts folder. I am trying to run
gpu-hello program on it using the following command
".
Hello Gabe Black, Jason Lowe-Power, Nikos Nikoleris, Andreas Sandberg,
I'd like you to reexamine a change. Please visit
https://gem5-review.googlesource.com/11195
to look at the new patch set (#6).
Change subject: base: Add an asymmetrical Coroutine class
..
* 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-rv64f/o3-timing:
FAILED!
*
build/RISCV/tests/opt
