[parsec-users] Questions about provided binaries (dedup & freqmine)

Christian Bienia cbienia at CS.Princeton.EDU
Wed Jun 2 13:29:54 EDT 2010

Hi Junjie,

About dedup: The program needs a lot of memory. 2 GB is not enough, you
should rather aim for 8 GB. You can easily make it run in your simulator by
increasing the parameter which determines the amount of RAM of your
simulated machine. I have written a somewhat more memory-efficient version
of dedup but it's not quite ready yet. It'll be released with the next
version of PARSEC.

About freqmine: You're right, the binary created by the gcc-hooks build
config is in fact serial due to a bug in the script. I'm not going to update
the official binary packages on the PARSEC website but I'll send you the new
freqmine binary directly by email.


-----Original Message-----
From: parsec-users-bounces at lists.cs.princeton.edu
[mailto:parsec-users-bounces at lists.cs.princeton.edu] On Behalf Of Junjie Wu
Sent: Tuesday, June 01, 2010 7:50 PM
To: parsec-users at lists.cs.princeton.edu
Subject: [parsec-users] Questions about provided binaries (dedup & freqmine)

Hello everyone,

I successfully compiled and ran all the cases natively under x86, but 
I'm now using SIMICS to simulate a sparc structure with solaris 10. The 
uname -a information:
SunOS abisko 5.10 Generic_120011-14 sun4u sparc SUNW,Sun-Fire

I don't want to manually compile everything inside the simulator, and I 
don't have a sparc machine either. Therefore, I downloaded the provided 
binary from the website. I use parsecmgmt to run my test (bin/parsecmgmt 
-a run -p <case> -c gcc-hooks -x pre -i <size> -n <nthreads>)

I have following problems:

[HOOKS] PARSEC Hooks Version 1.2
[DataProcess] Memory allocation failed.

The simulated machine has 2GB memory. Is that enough? I didn't have this 
problem when running dedup under x86 (compiled myself).

Based on my experience working with x86, I'm pretty sure the provided 
gcc-hooks binary is not a parallel one. The speedups I got was always 
1.00xx, no matter how many threads I was using. The default gcc-hooks 
config calls openmp config, but that openmp config never specifies the 
-fopenmp flag. I also got confirmation from someone else running the 
provided sparc-solaris binaries. It's trivial to resolve the issue, but 
since I can't recompile it in simulator, I want to request an update on 
the official binary. I don't think a serial gcc-hooks version is 
intended. Just for anyone interested:
CFLAGS="${CFLAGS} -fopenmp"
to pkgs/apps/freqmine/parsec/gcc-hooks.bldconf will do the trick. Though 
this might not be a nice way.

I'd really appreciate any thoughts on the two problems.

Junjie Wu
parsec-users mailing list
parsec-users at lists.cs.princeton.edu

More information about the parsec-users mailing list