-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The gem5 is no longer compatible #4
Comments
I also have the same problem using NVMain with gem5. |
I got the same issues when applying the latest version of NVMain with latest update on gem5 When compiling with NVMain, it raises:
|
The way to fix it was to use older commit or edit the code with new
function call names
On Thu, Apr 9, 2020 at 10:51 PM Fangzhou Liu (Jerry) < ***@***.***> wrote:
I got the same issues when applying the latest version of NVMain with
latest update on gem5
[gem5 commit id: 135595a4d79a30d715be64d3a2833a28434699c7].
When compiling with NVMain, it raises:
- 'BaseSlavePort' does not name a type; did you mean 'SlavePort'?
- no matching function for call to 'Packet::Packet(Request*&,
MemCmd::Command)
- class Packet' has no member named 'checkFunctional'
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AG6MWROMRMLUZDV5JVHOS3LRL2CUJANCNFSM4JEZS6WQ>
.
--
Thanks,
Abhishek Singh
PhD Student
Lehigh University
Remember "Chance favors the prepared mind."(Pasteur)
|
Hi Abhishek, I am getting the similar problem while building the latest version of gem5 with NVmain.
Could you please elaborate on what you mean by editing code with new function call names? Why is it an issue of the function call names? |
Hi Aditya,
Function names like Master and slave port have changed over the years, So
you need to edit those names or u can roll back to compatible previous
commit
Thanks,
Abhishek Singh
Ph.D. Student
Lehigh University
Remember "Chance favors the prepared mind."(Pasteur)
…On Wed, May 20, 2020 at 5:34 PM Aditya Narayan ***@***.***> wrote:
Hi Abhishek, I am getting the similar problem while building the latest
version of gem5 with NVmain.
1. no matching function for call to 'Packet::Packet(Request*&,
MemCmd::Command)'
2. 'class Packet' has no member named 'checkFunctional'
Could you please elaborate on what you mean by editing code with new
function call names? Why is it an issue of the function call names?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AG6MWRI3ZMDVYXP646DTJALRSREGTANCNFSM4JEZS6WQ>
.
|
Thank Abhishek, I see. Could you point me to previous gem5 version, if you are aware, that is compatible with such function names? |
@adityanarayan1191 Did you find the right gem5 version to be compatible? |
I can't find the commit with that hash |
I think the patch is generated by HG (mercurial). The number 11688 refers to a version number in mercurial source control system and the patch is supposed to be used by mercurial's However, since the HG repository is no longer available, I can't find any ideal way to roll back to the correct version. :( |
I tried this version with little modification. It can work. |
@adityanarayan1191 The errors mentioned above are caused by the following reasons:
@herochen11 Thanks! Theoretically, it should work, because your version had been committed just a few days before Jun 12 2018. It may be the last commit compatible with NVMain, provided that there is no sever bug with this version. Besides, what do you mean "little modification"? |
I think you'd better open a new issue and post more information there for others to reproduce. I'm not sure whether your problem has something to do with the compatibility between gem5 and NVMain. |
ok,thanks. |
Okay, so I figured it out and will briefly describe the steps I've taken since it really was a pain... Most of it comes from this slightly wired guide: https://www.codetd.com/en/article/9656074
At some point the build failed for me which was either because I accidentally used scons instead of scons2 or because I compiled gem5 before adding NVmain. Deleting the build folder of gem5 solved the problem. I hope this helps. |
Hi @seceng-jan, @AbhishekUoR and others, I tried to integrate gem5 with NVmain using the command: But I am facing the below error: Following are the versions of dependencies: Kindly suggest the way out. Thanks. |
Try with Python 2.7 and scons 2.5.1 |
The gem5 files situated in Simulators/gem5 are not compatible with the current commit of gem5.
Also, when used March 1 st 2017 commit, how do we build as the command in README causes an error unrecognized memory type NVMainMemory.
The text was updated successfully, but these errors were encountered: