Fix bug when debugging located variables of type memory (%M)
authorlaurent
Mon, 16 May 2011 11:57:41 +0200
changeset 292 a1d9c206409e
parent 279 c0453b7f99df
child 293 e53b93cd90e4
Fix bug when debugging located variables of type memory (%M)
stage4/generate_c/generate_var_list.cc
--- a/stage4/generate_c/generate_var_list.cc	Tue Apr 05 15:14:19 2011 +0200
+++ b/stage4/generate_c/generate_var_list.cc	Mon May 16 11:57:41 2011 +0200
@@ -110,6 +110,7 @@
       variable_vtc,
       external_vtc,
       located_input_vtc,
+      located_memory_vtc,
       located_output_vtc,
       array_vtc,
       structure_vtc,
@@ -216,6 +217,9 @@
         case located_input_vtc:
           s4o.print("IN");
           break;
+        case located_memory_vtc:
+          s4o.print("MEM");
+          break;
         case located_output_vtc:
           s4o.print("OUT");
           break;
@@ -484,6 +488,8 @@
 	  locationtype_t location_type = search_location_type.get_location_type(symbol->location);
 	  if (location_type == input_lt)
         this->current_var_type_category = located_input_vtc;
+      else if (location_type == memory_lt)
+        this->current_var_type_category = located_memory_vtc;
       else if (location_type == output_lt)
         this->current_var_type_category = located_output_vtc;