[gem5-users] Re: Compiling and running RISCV in SE mode

2022-04-30 Thread Felipe Vega
Sorry for being so stubborn Hoa, should I try to compile openmp statically or not, cause when I compile dynamically I get the "Someone allocated physical memory..."error, while the "syscall not implemented" appears when I use the statically built one. I tried redirecting the /proc directory since

[gem5-users] Re: Compiling and running RISCV in SE mode

2022-04-29 Thread Felipe Vega
Hi Hoa, Using the -static flag results in an output warning of: Using 'dlopen' in statically linked applications requires the shared libraries from the glibc version used for linking. Then on simulation: "fatal: syscall sched_getaffinity (#123) unimplemented". On 4/29/22, Hoa Nguyen wrote: > Hi,

[gem5-users] Re: Compiling and running RISCV in SE mode

2022-04-29 Thread Felipe Vega
Hi Boris, sorry I forgot some details: $ riscv64-unknown-elf-gcc helloworld.c -o binario.riscv ---> compiles and run. The thing the helloworld I use includes "#include" because my true workload needs this library. $ riscv64-unknown-elf-gcc helloworld.c -fopenmp -o binario.riscv ---> won't compile

[gem5-users] Re: Compiling and running RISCV in SE mode

2022-04-29 Thread Boris Shingarov
Felipe, What do `file` and `riscv-linux-gnu-objdump` (or whatever your cross-toolchain calls objdump) say about `binario.riscv`?  I don't know where that "--interp-dir sysroot" in your output came from, but it smells like we are dealing with dynamic-ELF here and I suggest you start from the m