On Mon, Sep 27, 2010 at 9:13 PM, avadh patel <[email protected]> wrote:
> > On Mon, Sep 27, 2010 at 8:15 PM, DRAM Ninjas <[email protected]> wrote: > >> Hello, >> >> So I'm trying to setup some Parsec runs from the image provided with >> MARSS, but I'm running into issues with the gcc-hooks build. It appears that >> the distribution doesn't have the ptlcall hooks in the gcc-hooks version of >> the binaries. When I try to add it by uninstalling the hooks package and >> recompiling it with ptlcalls, libtool doesn't seem to be interested in using >> the correct paths from the bldconf file (why you would distribute a >> benchmark suite with such weird default paths is beyond me, but I digress) >> when rebuilding the hooks package so it fails. >> >> The disk image contains just the default Parsec distribution. But we do > have one internal image that has modified hooks library in Parsec that works > with ptlcalls. Also this hooks library contains the default thread affinity > code for pthreads. > I am setting up the disk image for public distribution and will send you > the link to download it once its done. > I have uploaded the new parsec-roi disk image on the website. You can download it from here: http://marss86.org/index.php/Disk_Images#Image_with_Parsec_2.1_Benchmarks_and_ROI_Hooks . - Avadh > > Are you guys just running ./start_sim and avoiding using the gcc-hooks >> build or am I missing something since I'm clueless about libtool? >> >> In the default distribution we did something similar, but the one with > hooks enabled, we use ptlcalls to switch to simulation. > > - Avadh > > >> Thanks, >> Paul >> >> _______________________________________________ >> http://www.marss86.org >> Marss86-Devel mailing list >> [email protected] >> https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel >> >> >
_______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
