From e396a34b0155d5054a099c67a91baa66c095d3d8 Mon Sep 17 00:00:00 2001
From: Korey Sewell <ksewell@umich.edu>
Date: Fri, 4 Feb 2011 00:09:20 -0500
Subject: inorder: fault handling Maintain all information about an
 instruction's fault in the DynInst object rather than any cpu-request object.
 Also, if there is a fault during the execution stage then just save the fault
 inside the instruction and trap once the instruction tries to graduate

---
 src/cpu/inorder/pipeline_stage.cc | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

(limited to 'src/cpu/inorder/pipeline_stage.cc')

diff --git a/src/cpu/inorder/pipeline_stage.cc b/src/cpu/inorder/pipeline_stage.cc
index e10ceb326..744ffd4d2 100644
--- a/src/cpu/inorder/pipeline_stage.cc
+++ b/src/cpu/inorder/pipeline_stage.cc
@@ -944,12 +944,7 @@ PipelineStage::processInstSchedule(DynInstPtr inst,int &reqs_processed)
                         "completed.\n", tid, inst->seqNum, 
                         cpu->resPool->name(res_num));
 
-                if (req->fault == NoFault) {
-                    inst->popSchedEntry();
-                } else {
-                    panic("%i: encountered %s fault!\n",
-                          curTick(), req->fault->name());
-                }
+                inst->popSchedEntry();
 
                 reqs_processed++;                
 
-- 
cgit v1.2.3