Re: [gem5-users] RISC-V DerivO3CPU: Assertion `atomicOpFunctor != NULL' failed

Hi Hossein, I'm glad you were able to find a solution to your problem. The best way to post code and try to get it merged is to create a patch on Gerrit , which is the patch review system gem5 uses. The CONTRIBUTING file has instructions on how to do that,

Re: [gem5-users] RISC-V DerivO3CPU: Assertion `atomicOpFunctor != NULL' failed

Forwarding a possible solution: -- Forwarded message - Hi Hossein, I don't know if there is an update to this on you end, but here is how I got around this issue when I tried running some SPEC benchmarks compiled for RISC-V on DerivO3CPU. I guess the problem is related to how

[gem5-users] RISC-V DerivO3CPU: Assertion `atomicOpFunctor != NULL' failed

Hi, I'm using gem5 for simulation of cross-compiled RISC-V programs. I receive the following error when using the DerivO3CPU model: gem5.opt: build/RISCV/mem/request.hh:678: AtomicOpFunctor* Request::getAtomicOpFunctor(): Assertion `atomicOpFunctor != NULL' failed. I have used this command: