fix: disable assertion failure caused by speculative instructions. (#64)

A better way would be to add a speculative flag to these instructions instead of checking these assertions for these instructions

components/MMU/pageWalk.cpp

@@ -266,7 +266,8 @@ PageWalk::InitialTranslationSetup(TranslationTransport& aTranslation)
 
     // Handle a case where for Linux, the page table of EL0 is in EL1's register.
     if (EL == 0) {
-        DBG_Assert(statefulPointer->isBR0);
+        // There might be speculative memory accesses, so the following check may not be passed.
+        // DBG_Assert(statefulPointer->isBR0);
         EL = 1;
     };
 

components/uArch/CoreModel/arbiter.cpp

@@ -492,7 +492,8 @@ CoreImpl::scanAndBlockMSHR(memq_t::index<by_insn>::type::iterator anLSQEntry)
     // Check for an existing MSHR for the same address (issued this cycle)
     MSHRs_t::iterator existing = theMSHRs.find(anLSQEntry->thePaddr);
     if (existing != theMSHRs.end()) {
-        DBG_Assert(!existing->second.theWaitingLSQs.empty());
+        // Maybe the original load was a speculative load that was annulled
+        // DBG_Assert(!existing->second.theWaitingLSQs.empty());
         existing->second.theBlockedOps.push_back(anLSQEntry->theInstruction);
         return true;
     }