Fix reporting of specs settings in tracefile

- Seems like an `(int&)` cast was necessary to correctly trace the value
of the enum ?
- pyspecs was updated to use the available top-level values instead of
  convoluted checks

1 files changed, 6 insertions, 6 deletions

diff --git a/src/specs.h b/src/specs.h
index fe56d6a..f2ae80a 100644
--- a/src/specs.h
+++ b/src/specs.h
@@ -73,10 +73,10 @@ public:
     };
 
     enum AnalysisType {
-        ANALYSIS_TYPE_MINVAL,
-        CW_OPERATING_POINT,
-        CW_SWEEP,
-        TIME_DOMAIN,
+        ANALYSIS_TYPE_MINVAL = -1,
+        CW_OPERATING_POINT = 0,
+        CW_SWEEP = 1,
+        TIME_DOMAIN = 2,
         ANALYSIS_TYPE_MAXVAL,
 
         // aliases
@@ -114,7 +114,7 @@ public:
 
     // other
     sc_signal<bool, SC_MANY_WRITERS> drop_all_events;
-    bool verbose_component_initialization = true;
+    bool verbose_component_initialization = false;
 
     SPECSConfig(sc_module_name name);
 
@@ -156,4 +156,4 @@ public:
     sc_trace(sc_trace_file *tf, const SPECSConfig &s, string parent_tree);
 };
 
-extern SPECSConfig specsGlobalConfig;
\ No newline at end of file
+extern SPECSConfig specsGlobalConfig;