[gem5-users] Re: fatal: Syscall 278 out of range (ARM) - can i skip/supress syscall unimplemeted errors

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

[gem5-users] Re: fatal: Syscall 278 out of range (ARM) - can i skip/supress syscall unimplemeted errors

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

[gem5-users] Re: fatal: Syscall 278 out of range (ARM) - can i skip/supress syscall unimplemeted errors

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 I understand, ArmISA.py was not exposed into configuration

[gem5-users] Re: fatal: Syscall 278 out of range (ARM) - can i skip/supress syscall unimplemeted errors

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