How does parsec work

Quintin Fettesunread,Jan 4, 2019, 2:57:12 PM1/4/19to Sniper simulatorI was able to get the benchmarks (only Parsec and Splash) to compile on Ubuntu 18.04; I'll provide instructions below. HOWEVER, a few are broken at runtime and others have some general weirdness that makes me weary of using them. The recent support for newer operating systems in snipersim has been great so far. Will the benchmarks provided at [ also be modified to support new operating systems "out of the box?" This would be incredibly useful for the work I'm performing if I could run these benchmarks with confidence that they are working correctly.Instructions for compiling Parsec and Splash benchmarks on Ubuntu 18.04:Edit benchmarks/MAKEFILE ; This only fixed parsec and splash 2, I did not attempt to fix cpu2006 or npb, and both will fail to compile. comment out the following lines:make -C cpu2006make -C npbmake -C localmake -C cpu2006 cleanmake -C npb cleanmake -C local cleanEdit benchmarks/parsec/parsec-2.1/pkgs/apps/bodytrack/parsec/gcc-sniper.bldconfAddCXXFLAGS="-std=gnu++98 ${CXXFLAGS} ${HOOKS_CXXFLAGS}"Edit src files in ferret. Replace all instances of HUGE with HUGE_VAL. The files needing modified are listed belowbenchmarks/parsec/parsec-2.1/pkgs/apps/ferret/src/src/lsh/LSH_query.cbenchmarks/parsec/parsec-2.1/pkgs/apps/ferret/src/src/lsh/LSH_query_batch.cbenchmarks/parsec/parsec-2.1/pkgs/apps/ferret/src/benchmark/ferret-parallel.cbenchmarks/parsec/parsec-2.1/pkgs/apps/ferret/src/benchmark/ferret-serial.cEdit benchmarks/parsec/parsec-2.1/pkgs/tools/cmake/parsec/gcc-sniper.bldconfModify line 8 to read (added -std=gnu++98 flag):build_env="CC="${CC}" CXXFLAGS="-std=gnu++98 ${CXXFLAGS} -fexceptions" LDFLAGS="-L${CC_HOME}/lib64 -L${CC_HOME}/lib -L${PARSECDIR}/pkgs/libs/hooks/inst/${PARSECPLAT}/lib""Edit benchmarks/parsec/parsec-2.1/pkgs/apps/x264/parsec/gcc-sniper.bldconf Add CC="${HOOKS_CC} -no-pie"RUN MAKE. IT WILL FAIL. WHEN IT GETS TO THE SSL LIBRARY. THE ERROR WILL READ: smime.pod around line 272: Expected text after =item, not a numbersmime.pod around line 276: Expected text after =item, not a numbersmime.pod around line 280: Expected text after =item, not a numbersmime.pod around line 285: Expected text after =item, not a numbersmime.pod around line 289: Expected text after =item, not a numberThis is the only error I couldn't fix before running make once because the src is not downloaded prior to the first run of makeEdit benchmarks/parsec/parsec-2.1/pkgs/libs/ssl/src/Makefile.orgLine 612 is:install: all install_docs install_swchange it to:install: all install_swThis is a hack I found online. It just prevents the docs from being compiledRun make again. the benchmarks should now compile correctlyThe pin2 branch (to my knowledge) doesn't compile correctly on Ubuntu 18.04. This step is only necessary for the pin3 branchin benchmarks/run-sniper comment out lines 138-140, which areif not os.path.exists(os.path.realpath(os.path.join(graphiterootdir, 'lib', 'pin_sim.so'))): print '\nERROR: Sniper

Has not been compiled. Please compile Sniper before trying to run an application.\n' sys.exit(1)in benchmarks/run-sniper comment out lines 154-156, which are:if not os.path.exists(os.path.realpath(os.path.join(graphiterootdir, 'lib', 'pin_sim.so'))): print '\nERROR: Sniper has not been compiled. Please compile Sniper before trying to run an application.\n' sys.exit(1)I hope this is helpful to other people, and I hope it can get us closer to official support on newer operating systems for these benchmarks!Dan Recherunread,Jan 28, 2019, 12:50:44 PM1/28/19to Sniper simulatorHi Quintin,I tried to do as you described,in step 3 I didn't find directory benchmarks/parsec/parsec-2.1/pkgs/apps/ferret/src/src/lsh/LSH_query.c what I am doing wrong?Thanks,DanQuintin Fettesunread,Jan 29, 2019, 2:51:43 PM1/29/19to Sniper simulatorIt could be that I made a mistake in my instructions and you have to run make once so that the files download. Try performing the previous steps then running make one and see if the files appear.Dan Recherunread,Feb 2, 2019, 9:20:21 AM2/2/19to Sniper simulatorthanks,I fount the files after make :)The Turing Projectunread,Feb 4, 2019, 6:12:53 AM2/4/19to Sniper simulatorhello i have make that procedure and i have a probleme during the end of compilation, it doesnt find benchmarks/parsec/parsec-2.1/gcc -I/home/chapoul/sniper-7.1/benchmarks/parsec/parsec-2.1/pkgs/libs/ssl/inst/amd64-linux.gcc-sniper/include -I/home/chapoul/sniper-7.1/benchmarks/parsec/parsec-2.1/pkgs/libs/zlib/inst/amd64-linux.gcc-sniper/include -O3 -funroll-loops -fprefetch-loop-arrays -static-libgcc -Wl,--hash-style=both,--as-needed -DPARSEC_VERSION=2.1 -DENABLE_PARSEC_HOOKS -I/home/chapoul/sniper-7.1/benchmarks/parsec/parsec-2.1/pkgs/libs/hooks/inst/amd64-linux.gcc-sniper/include -I/home/chapoul/sniper-7.1/benchmarks/parsec/tools/hooks -I/include -DENABLE_PARMACS -Wall -std=c99 -fno-strict-aliasing -D_XOPEN_SOURCE=600 -DPARALLEL -pthread -L/home/chapoul/sniper-7.1/benchmarks/parsec/parsec-2.1/pkgs/libs/ssl/inst/amd64-linux.gcc-sniper/lib -L/home/chapoul/sniper-7.1/benchmarks/parsec/parsec-2.1/pkgs/libs/zlib/inst/amd64-linux.gcc-sniper/lib -L/usr/lib64 -L/usr/lib -L/home/chapoul/sniper-7.1/benchmarks/parsec/parsec-2.1/pkgs/libs/hooks/inst/amd64-linux.gcc-sniper/lib -uparmacs_roi_end -uparmacs_roi_start -L/home/chapoul/sniper-7.1/benchmarks/parsec/tools/hooks -lhooks_base -lrt -pthread -o dedup hashtable.o queue.o util.o binheap.o tree.o decoder.o dedup.o rabin.o encoder.o -lhooks -lcrypto -lz/usr/bin/ld : ne peut trouver -lhooks_basecollect2: error: ld returned 1 exit statuspkgs/libs/ssl/src/Makefile.orgThe Turing Projectunread,Feb 4, 2019, 7:36:27 AM2/4/19to Sniper simulatorLe vendredi 4 janvier 2019 21:57:12 UTC+1, Quintin Fettes a écrit :ahmad sedighunread,Oct 24, 2019, 11:54:35 AM10/24/19to Sniper simulatorahmad sedighunread,Oct 24, 2019, 7:16:46 PM10/24/19to Sniper simulatorHi Quintin,i recommend -std=gnu++17 or 11 at step 2 and 4. RegardsKleber Krugerunread,Sep 6, 2020, 12:27:18 AM9/6/20to Sniper simulatorJagadeesh Samalaunread,Sep 8, 2020, 3:01:44 AM9/8/20to Sniper simulatorI am able to run parsec but facing the following issue while building the SPLASHPlease help me. Also, can anyone provide the information related to all the input parameters required for the simulation.Zilmarij Iqbalunread,Jun 20, 2021, 2:41:29 AM6/20/21to Sniper simulatorHi,I followed the steps till Step5, then did make and encountered the following error (couple of these):benchmarks/parsec/parsec-2.1/./pkgs/apps/vips/src/libsrcCC/vipsc++.cc:5483:37: error: ISO C++1z does not

So I want to be able to use parsec on my deskto. The problem is is that unless I turn my computer on and log into it at least one time I cannot get the application to boot up. This morning I forgot to turn it on before leaving I had my girlfriend turn on my computer but I can't access my computer. I only way right now getting it to wake is to set wake time events to wake it up from sleep. The problem with this method has been that it will turn my computer on when I have no intention of using parsec for the day. And trying to initiate a parsec connection does not trigger a wake on lan event to wake up the computer. That's my dilemma how can I activate a wake timer on my computer with an event that's triggered by user action and not by a timed event. So that I can log into my computer immediately put it to sleep and then wake it up at will. I have wake on lan enabled on my ethernet device and in the BIOS I'm pretty sure. -, edit just found out she never turned it on so this might not even be a problem.

Suite is to bebuilt and executed in one run without cleaning up intermittently.The PARSEC benchmarks have been parallelized with pthreads, OpenMP, TBB andatomic instructions. Many workloads support more than one parallelization. Eachparallelization has its own requirements that have to be fulfilled in order tobe able to build and run workloads that use it. By default only support forpthreads and OpenMP are needed. Gcc supports OpenMP since version 4.2.0.PARSEC has been successfully tested on the following systems:Linux/i386Linux/x86_64Linux/ItaniumSolaris/SparcLimited support exists for the following platforms, but not all benchmarkprograms might be available:Darwin/PowerPCUsagePARSEC ships with several tools which are installed in the 'bin/' directory.You can use them to customize and manage your installation of the benchmarksuite. 'parsecmgmt' is the main tool. Its purpose is to build and runpackages as well as perform other management operations. 'bldconfadd' and'bldconfdel' can be used to create and delete your own build configurations.When you build and run PARSEC with 'parsecmgmt', it will create a log filewhich will contain all output in the 'log/' directory. You can get a helpsummary for each tool by invoking it with option '-h'.A full set of man pages documenting PARSEC, its tools and the most importantparts of the source code is given in the man/' directory. If you add the bin/' directory to the PATH environment variable and the man/' directory to the MANPATH variable then all tools and man pages are accessible at the command line without having to specify the full path every time. A bash shell script env.sh' is provided in the root directory of the PARSEC distributionwhich modifies the environment in that way. If you work with the bash shell youcan make use of it before you start working with PARSEC by executingsource env.sh'. You can then start browsing the documentation by running man parsec'. Support for other shells is currently not available.The following examples assume that the 'bin/' directory of PARSEC is in yourpath.How to Build PARSECBefore compiling the PARSEC benchmarks, please change some variables in thefile "config/gcc.bldconf" such that the PARSEC command can locate thecompiler path correctly.To compile all programs of the benchmark suite with the default configuration,simply