One of the merits of my fork is that I clearly documented what works
and what does not unlike other repos I've seen so far.
Therefore, you can immediately see on the readme that Raytrace and
Vips didn't work and how they failed.
My setup might work for native QEMU aarch64 compile, but I haven't
the problem is that i tried to compile parsec by cross compiler but i found
the previous error, so i do not know is what i forgot something in my
is there another build version that works with aarch64 directly?
because I found a version in this link but I'm not
You can compile parsec by using either cross compiler or qemu and add
binary benchmark into linaro image.
I am not sure if Ciro’s parsec can compile all benchmark for aarch64 but I
could not. At least Raytrace and Vips are not compiled with patches.
On Sat, May 12, 2018 at 9:00 AM commerce
I ran a simple multithreaded helloworld code (as enclosed) with ARM I got
"Panic:Page table fault when accessing virtual address" error.
Then I tried running on X86 and it runs fine but in stats file I get
"sim_seconds 18446744.073710" which is impossible.
I used 4 cores as there are 4
My setup uses a cross compiled PARSEC and builds the roots from
scratch with buildroot, see README for instructions.
On Sat, May 12, 2018 at 5:00 PM, commerce _com wrote:
> hi Ciro;
> so i downloaded parsec which is in the link you sent me but did i copy it
so i downloaded parsec which is in the link you sent me but did i copy it
directly into the linaro arch64 image or i add the patch for arch64 i did
not understand well ??
because I need to copy parsec 3.0 in the linaro image to run with gem5.
2018-05-12 17:28 GMT+02:00 Ciro
I don't think those patches are enough to run all benchmarks, and I
have never seen a set of patches that just worked for all benchmarks so far.
I have part of parsec benchmarks working at:
I need to compile parsec 3.0 with Cross-Compile:
here are the steps that I followed:
I downloaded gcc-linaro-5.5.0-2017.10-x86_64_aarch64-linux-gnu and I
modified the xcompile-patch.diff file as follows:
* # CC_HOME is root installation of the C compiler*
*- export CC_HOME = "/ usr"*
For my work, I had to implement three-levels of caches with LLC as a shared
cache. I preferred to extend the classical memory model rather than ruby,
because ruby did not support three-level coherence protocol. After
modelling L3 cache I further made a lot more changes to the classical
Immediately we suspect that the file is auto-generated during build.
So we do a shell find in the output directory:
find . -name OpClass.hh
This leads us to: ./build/ARM/enums/OpClass.hh
Open the file, look for interesting unique identifiers, and git grep
that on main source.
Mail list logo