How did you cross compile PARSEC exactly? It requires patches to do so AFAIK.
I have most of splash2x working at: https://github.com/ cirosantilli/linux-kernel-module-cheat/tree/52358543846d7d9524c79908638951 d8a9bbdb64#parsec-benchmark (except some documented segfaults), and the patches are at: https://github.com/cirosantilli/parsec-benchmark Part of my patches are based on: https://github.com/arm- university/arm-gem5-rsk/tree/aa3b51b175a0f3b6e75c9c856092ae 0c8f2a7cdc/parsec_patches Does the problem happen for all tests, or just ferret? Can you try with some splash2x ones, which I know to be working. Have you added the magic instrumentation instructions to the ROI hooks? If yes, ensure that they are correct. Also, please send copy pastes of the terminal whenever possible instead of images, as google can index them. On Fri, Mar 30, 2018 at 4:29 PM, Timon Evenblij <evenblij.ti...@gmail.com> wrote: > Hi all, > > So I cross-compiled some parsec bechmarks, e.g. ferret. First I tried > putting them in the disk image that gem5 uses to boot, but that did not > work out (inodes were not readable or something, see my other mail thread). > Jason suggested then to use a second disk image and add it to the > simulation. In the simulation, mount the disk and proceed from there. > > So I executed this approach, which works better, as I can execute the > commands for the benchmark. However, I get an error saying illegal > instruction on the line where parsecmngmt tries to execute the benchmark > itself: > > > > The file command gives the following result: > >> file pkgs/apps/ferret/inst/arm-linux.gcc-hooks/bin/ferret >> pkgs/apps/ferret/inst/arm-linux.gcc-hooks/bin/ferret: ELF 32-bit LSB >> executable, ARM, version 1 (SYSV), statically linked, for GNU/Linux 2.6.32, >> not stripped > > > Which looks fine to me, as I want static 32 bit armv7 binaries to run on > gem5 ARMv7 simulations. > Any suggesting as to what mistake I could have made? Or could it be that > parsec has no support for armv7 on gem (some crucial instruction not > implemented? But this seems unlikely) > > Best regards > > Timon > > _______________________________________________ > gem5-users mailing list > gem5-users@gem5.org > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
