Thanks a lot! This make sense! On Fri, May 20, 2022 at 10:53 AM Giacomo Travaglini < giacomo.travagl...@arm.com> wrote:
> Hi Chant > On 5/20/22 16:34, Chant Zine wrote: > > I had the same error. It seems a recent upgrade to GCC-11 cross compiler > from arm results in this error. The GCC-10 version would work. > > Though not the culprit, I want to ask if there is a way to ensure to run > 64-bit emulated process. > > > As long as the binary is compiled for AArch64, the 64-bit process will be > automatically chosen > > > As I understand, ArmISA.py was not exposed into configuration files. So if > I don't change these py (which seems to require recompilation of gem5), I > will be running the default ArmISA in the SE simulation with following > features > class ArmDefaultSERelease(ArmRelease): > extensions = [ > 'CRYPTO', > # Armv8.1 > 'FEAT_LSE', 'FEAT_RDM', > # Armv8.2 > 'FEAT_SVE', > # Armv8.3 > 'FEAT_FCMA', 'FEAT_JSCVT', 'FEAT_PAuth', > # Other > 'TME' > ] > > But is there control over AArch64 vs ARMv7 32bit? Is ARMv7 only existing > in older versions of Gem5? > > > As mentioned before, in syscall emulation the execution mode is > automatically detected from the guest binary. Regarding your second > question, gem5 implements Armv8. Armv8 does support 32bit mode anyway; it > is called AArch32 and it is more or less Armv7 compatible. So yes, it is > possible to run arm 32-bit binaries in gem5 > > > Kind Regards > > > Giacomo > > On Mon, May 9, 2022 at 10:12 AM Jason Lowe-Power <ja...@lowepower.com> > wrote: > >> Hi Tom, >> >> My guess is that you're using a newer version of GLIBC which calles >> different syscalls than the versions of GLIBC that have been tested with >> gem5. I believe 278 is mq_notify. You can try to update the syscall >> implementation to ignore the syscall and see if the application still >> works. See >> https://gem5.googlesource.com/public/gem5/+/refs/heads/develop/src/arch/arm/linux/se_workload.cc#404 >> >> Another possibility is that you're using a 32-bit emulated process with a >> 64-bit binary, or something has gone wrong with whether it's detected as >> Arm32 or Arm64. In the 64-bit version, 278 is getRandom, which is >> implemented. See >> https://gem5.googlesource.com/public/gem5/+/refs/heads/develop/src/arch/arm/linux/se_workload.cc#762 >> >> Hope this helps! >> >> Cheers, >> Jason >> >> On Fri, May 6, 2022 at 6:33 PM <tomjosekalloo...@gmail.com> wrote: >> >>> Hi All, >>> >>> I am trying to run dhrystone benchmark on ARM and i get the following: >>> >>> ./build/ARM/gem5.opt --debug-flags=Exec >>> --debug-file=dhrystone_10k_a77_trace ./configs/example/arm/starter_se.py >>> --cpu minor --cpu-freq 3.0GHz --mem-type DDR4_2400_8x8 >>> ./tests/dhrystone_10k >>> >>> gem5 Simulator System. http://gem5.org >>> >>> gem5 is copyrighted software; use the --copyright option for details. >>> >>> gem5 version 21.2.1.0 >>> >>> gem5 compiled Apr 27 2022 18:13:35 >>> >>> gem5 started May 7 2022 01:55:59 >>> >>> gem5 executing on eden, pid 4723 >>> >>> command line: ./build/ARM/gem5.opt --debug-flags=Exec >>> --debug-file=dhrystone_10k_a77_trace ./configs/example/arm/starter_se.py >>> --cpu minor --cpu-freq 3.0GHz --mem-type DDR4_2400_8x8 ./tests/dhrystone_10k >>> >>> info: 1. command and arguments: ['./tests/dhrystone_10k'] >>> >>> Global frequency set at 1000000000000 ticks per second >>> >>> warn: No dot file generated. Please install pydot to generate the dot >>> file and pdf. >>> >>> build/ARM/mem/mem_interface.cc:791: warn: DRAM device capacity (16384 >>> Mbytes) does not match the address range assigned (1024 Mbytes) >>> >>> build/ARM/mem/mem_interface.cc:791: warn: DRAM device capacity (16384 >>> Mbytes) does not match the address range assigned (1024 Mbytes) >>> >>> build/ARM/base/statistics.hh:280: warn: One of the stats is a legacy >>> stat. Legacy stat is a stat that does not belong to any statistics::Group. >>> Legacy stat is deprecated. >>> >>> build/ARM/base/statistics.hh:280: warn: One of the stats is a legacy >>> stat. Legacy stat is a stat that does not belong to any statistics::Group. >>> Legacy stat is deprecated. >>> >>> 0: system.remote_gdb: listening for remote gdb on port 7000 >>> >>> build/ARM/sim/simulate.cc:194: info: Entering event queue @ 0. Starting >>> simulation... >>> >>> build/ARM/sim/syscall_emul.cc:74: warn: ignoring syscall >>> set_robust_list(...) >>> >>> build/ARM/sim/mem_state.cc:443: info: Increasing stack size by one page. >>> >>> build/ARM/sim/syscall_emul.hh:1014: warn: readlink() called on >>> '/proc/self/exe' may yield unexpected results in various settings. >>> >>> Returning '/home/tom/Documents/gem5/tests/dhrystone_10k' >>> >>> build/ARM/sim/syscall_desc.hh:209: fatal: Syscall 278 out of range >>> >>> Memory Usage: 2237648 KBytes >>> >>> >>> This is my new install on a new machine. In my older machine, i had run >>> the dhrystone for loop count of 1 million without any error. The new >>> install uses the latest stable patch. >>> >>> Any help is appreciated. >>> >>> Regards, >>> >>> Tom >>> _______________________________________________ >>> gem5-users mailing list -- gem5-users@gem5.org >>> To unsubscribe send an email to gem5-users-le...@gem5.org >>> >> _______________________________________________ >> gem5-users mailing list -- gem5-users@gem5.org >> To unsubscribe send an email to gem5-users-le...@gem5.org >> > > _______________________________________________ > gem5-users mailing list -- gem5-users@gem5.org > To unsubscribe send an email to gem5-users-le...@gem5.org > > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > _______________________________________________ > gem5-users mailing list -- gem5-users@gem5.org > To unsubscribe send an email to gem5-users-le...@gem5.org >
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org
