Sorry for the confusion. Compiling with gcc works. I am able to use
m5_exit() after following the steps in my last reply.
Though I will also test your given steps.
Thank you Daniel.
On Sat, Aug 1, 2020, 3:51 PM Daniel Gerzhoy
wrote:
> What errors are you getting?
>
> I would separate that out
What errors are you getting?
I would separate that out further though.
Steps 1-3: Compile Each one separately
g++ -O2 -I/sam/gem5/util/m5/../../include -o m5op_x86.o -c m5op_x86.S
g++ -O2 -I/sam/gem5/util/m5/../../include -o m5_mmap.o -c m5_mmap.c
hipcc -g -O2 -I/sam/gem5/include -o 2DConvolution
Hi Daniel,
Actually compiling m5op_x86.o and m5_mmap.o fails with hipcc.
Gcc works fine. Here's my steps.
*Compilation Steps:*
g++ -O2 -I/sam/gem5/util/m5/../../include -o m5op_x86.o -c m5op_x86.S
g++ -O2 -I/sam/gem5/util/m5/../../include -o m5_mmap.o -c m5_mmap.c
/opt/rocm/hip/bin/hipcc --amdgp
Sorry, using hipcc* to link them together.
On Sat, Aug 1, 2020 at 2:15 PM Daniel Gerzhoy
wrote:
> I would suggest compiling M5op with gcc or g++ with a -c flag and then
> using M5op to link them together.
>
> On Sat, Aug 1, 2020 at 2:13 PM Sampad Mohapatra via gem5-users <
> gem5-users@gem5.org>
I would suggest compiling M5op with gcc or g++ with a -c flag and then
using M5op to link them together.
On Sat, Aug 1, 2020 at 2:13 PM Sampad Mohapatra via gem5-users <
gem5-users@gem5.org> wrote:
> Hello,
>
> While trying to compile polybench benchmarks with m5_exit(0) using the HIP
> compiler
