[gem5-users] Re: GCN3 docker file missing

2020-09-01 Thread Matt Sinclair via gem5-users
Hi Samaksh, The warnings you mentioned can be ignored. They are highlighting that the sched_yield syscall is not implemented in SE mode. Which is fine, it's not needed for correctly simulating this program on the GPU. I'm not quite sure what the other issue is though. It sounds like you are sa

[gem5-users] Re: GCN3 docker file missing

2020-09-01 Thread Samaksh Sethi via gem5-users
That error was arising because when the makefile wasn't running properly I was trying out alternate methods on my own, but now I'm using the makefile again since the patch was pushed, but it's still not working. I myself don't know why I have to use make and make square both myself, but the only wa

[gem5-users] Re: GCN3 docker file missing

2020-09-01 Thread Matt Sinclair via gem5-users
This appears to be the same error Dan mentioned previously, where you are using gcc instead of hipcc. Did you try applying the fix he suggested there? Having said that, the first few lines appear to be making square already, so I'm not sure why you are trying to make it again? Matt On Tue, Sep

[gem5-users] Re: GCN3 docker file missing

2020-09-01 Thread Samaksh Sethi via gem5-users
Hi Matt, I had originally sent that message before the changes were implemented, so, now the "make" command seems to work (I'm not completely sure from the output) but "make square" is still stuck where it was before (As previously posted before at https://www.mail-archive.com/gem5-users@gem5.org/m

[gem5-users] Re: GCN3 docker file missing

2020-08-31 Thread Matt Sinclair via gem5-users
Hi Samaksh, Is this stuff you tried before or after the message Bobby sent? Thanks, Matt On Mon, Aug 31, 2020 at 2:09 PM Samaksh Sethi via gem5-users < gem5-users@gem5.org> wrote: > Ok so, doing this, on the first run, square.o is not created properly, but > that error goes away on the 2nd run,

[gem5-users] Re: GCN3 docker file missing

2020-08-31 Thread Bobby Bruce via gem5-users
Yes, the gem5-resources was wrong, but I think this commit fixes the issues here? https://gem5-review.googlesource.com/c/public/gem5-resources/+/33555 It has just been merged, so if you pull the latest version I think this should compile. -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Dav

[gem5-users] Re: GCN3 docker file missing

2020-08-31 Thread Samaksh Sethi via gem5-users
Ok so, doing this, on the first run, square.o is not created properly, but that error goes away on the 2nd run, and now there's a new error, which I have no clue about how to fix ("make gfx8-apu" gives the same error too), as it's probably something in the docker file. Hope I'm not missing anything

[gem5-users] Re: GCN3 docker file missing

2020-08-31 Thread Matt Sinclair via gem5-users
Kyle, can you please fix this (the Makefile) for square? Or update the instructions in the way Dan described above? Matt On Mon, Aug 31, 2020 at 11:51 AM Daniel Gerzhoy via gem5-users < gem5-users@gem5.org> wrote: > Looks like that command needs to be updated, or the makefile. > > Try the comma

[gem5-users] Re: GCN3 docker file missing

2020-08-31 Thread Daniel Gerzhoy via gem5-users
Looks like that command needs to be updated, or the makefile. Try the command without "square" at the end (" docker run --rm -v $PWD/gem5-resources:/gem5-resources -w /gem5-resources/src/square make ") If you look in the makefile the first rule is "gfx8-apu" not "square" so you could also change

[gem5-users] Re: GCN3 docker file missing

2020-08-31 Thread Samaksh Sethi via gem5-users
Ok so I forgot to mention that the gem5-resources repository ( https://gem5.googlesource.com/public/gem5-resources/) doesn't have the makefile in the main folder, it's actually in gem5-resources>>src>>square, so I can't just run the command (docker run --rm -v $PWD/gem5-resources:/gem5-resources -w

[gem5-users] Re: GCN3 docker file missing

2020-08-30 Thread Daniel Gerzhoy via gem5-users
Samaksh, Yep, thats precisely what I've been doing. Using the docker from the develop branch, and then the simulator is the staging branch. It actually looks like you pointed the simulator onto the square.cpp source file rather than the square.out (or whatever your compiler outputs). Not sure if

[gem5-users] Re: GCN3 docker file missing

2020-08-30 Thread Matt Sinclair via gem5-users
Dan or Kyle can confirm, but yes I believe that is what others are doing. If you look through the posted text from running square, you have a fatal error because of it being able to access gem5-resources. Kyle, have you seen this before? Matt On Sun, Aug 30, 2020 at 5:43 PM Samaksh Sethi via ge

[gem5-users] Re: GCN3 docker file missing

2020-08-30 Thread Samaksh Sethi via gem5-users
Okay, yeah that does make sense to me. So what i understand is, I used the develop branch for the dockerfile and then I run everything as usual from the staging branch Ok, so that works, Thanks a lot!! I was able to get the build command running, Just one last thing, how do I confirm everything w

[gem5-users] Re: GCN3 docker file missing

2020-08-30 Thread Matt Sinclair via gem5-users
Ok, we can try to make it clear that you should be looking at the develop branch. I thought the docker was pointing to the GCN3 staging branch, despite being on the develop branch, but that error is likely what this pending patch is fixing: https://gem5-review.googlesource.com/c/public/gem5/+/3365

[gem5-users] Re: GCN3 docker file missing

2020-08-30 Thread Samaksh Sethi via gem5-users
Thanks! That itself was my issue, I didn't understand from the documentation that I had to clone the develop branch, I was just using the master branch! But I'm still getting errors just running build commands directly from the documentation https://youtu.be/HhLiMrjqCvA - This is the guide I'm fol

[gem5-users] Re: GCN3 docker file missing

2020-08-30 Thread Matt Sinclair via gem5-users
Can you please provide us with some additional information about how you are attempting to run it? For example, what branch are you using? Looks like there is an extra 'o' in that link, thanks -- Kyle can you please fix this? To the best of our knowledge, the Docker is working, so I suspect ther