Open SteliosKaragiorgis opened 1 year ago
So is it better to upload the PRs on Ripes https://github.com/mortbopet/Ripes/pull/290 without my VSRTL changes and then add them?
Before considering PRs into either repository you need to address the above comments. This will require that you sit down, look at your current implementation, identify where you're adding things into VSRTL that shouldn't be in VSRTL (as described above) and then figure out a way to reimplement that either:
I cannot stress this enough. Whereever you have non-generic code inside VSRTL this is an indication that you need to change that code. VSRTL is a framework and thus implementation-specific logic should not be anywhere within the framework.
And the same goes with an eventual Ripes PR. If you study the current Ripes codebase you will see that ISA-specific information is only found in two places:
So similarly, wherever your code does not follow this pattern means that you'll have to refactor it.
Okay. First I will try to reimplement it outside the VSRTL. I think I tried it again on the past but I will try again.
The problem is that I added some lines that cointains some things from Ripes, correct?
Like if(QString::fromStdString(m_component->getHierName()).contains("MIPS"))
Do you want first to upload my PRs on Ripes without the VSRTL changes?
The problem is that I added some lines that cointains some things from Ripes, correct? Like if(QString::fromStdString(m_component->getHierName()).contains("MIPS"))
Correct!
Do you want first to upload my PRs on Ripes without the VSRTL changes?
If you have small, atomic, PRs which do not depend on the changes in VSRTL, and represent incremental improvements to Ripes, then by all means, go ahead and submit those PRs! :)
Yes I have small PRs ready to upload but I have some tests that fail because it is for different ISA. I mentioned exact the prblem here: https://github.com/mortbopet/Ripes/pull/290
I reuploaded it. I removed the comments and it is qt6. Also it is working fine with the Ripes