We just ran into this ourselves very recently. We haven't tracked it down,
but our suspicion is that there's a bug in the default Ruby protocol
(MI_example) that is somehow triggered by the newer version of glibc, or
perhaps by the code generated by the newer version of gcc.
Please try another Ru
Hi all
I am trying to sharing the LSQ between all cores in O3CPU.
After reading python and C++ files, I understand that LSQ is part of
dcacheport and IEW stage of a CPU. Also lsq need to be associated with a
CPU.
Using the same lsq pointer doesn't work. Is there any other way to solve
this probl
Hi all,
I recompiled the "Hello World" test program, to ensure that future programs
work properly and I encountered an issue, when running it with ruby in
SE-mode.
Running on only one core worked, but produced the output
info: Increasing stack size by one page.
warn: ignoring syscall access(0, 48
