Disable AOCL_VERBOSE feature

- AOCL_VERBOSE implementation is causing breakage in libFLAME.
    Currently DTL code is duplicated in BLIS and libFLAME,
    Which results in duplicate symbol errors when DTL is enabled
    in both the libraries.

  - It will be addressed by making DTL as separate library.

  - The input logs can still be enabled by setting
    AOCL_DTL_LOG_ENABLE = 1 in aocldtlcf.h and recompiling
    the BLIS library.

AMD-Internal: [CPUPL-2101]
Change-Id: I8e69b68d53940e306a1d16ffbb65019def7e655a

aocl_dtl/aocldtl.c

@@ -59,7 +59,7 @@ AOCL_FLIST_Node *gpLogFileList = NULL;
 
 
 /* Global flag to check if logging is enabled or not */
-Bool gbIsLoggingEnabled = FALSE;
+Bool gbIsLoggingEnabled = TRUE;
 #endif
 
 #if AOCL_DTL_AUTO_TRACE_ENABLE
@@ -130,7 +130,7 @@ void DTL_Initialize(
 #if (AOCL_DTL_LOG_ENABLE || AOCL_DTL_DUMP_ENABLE)
     
     /* Check if DTL logging is requested via envoronment variable */ 
-    gbIsLoggingEnabled = bli_env_get_var( "AOCL_VERBOSE", FALSE );
+    gbIsLoggingEnabled = bli_env_get_var( "AOCL_VERBOSE", TRUE );
 #endif
 
 #if AOCL_DTL_AUTO_TRACE_ENABLE

aocl_dtl/aocldtlcf.h

@@ -20,21 +20,9 @@
    enable this macro by making it to 1 else 0 */
 #define AOCL_DTL_DUMP_ENABLE        0
 
-/*
- * Logging of inputs can be enabled by two methods:
- *
- * 1. Using environment variable AOCL_VERBOSE.
- * 2. APIs AOCL_DTL_Enable_Logs(), AOCL_DTL_Disable_Logs()
- * 
- * The API takes precedence over environment variable.
- * 
- * The global flag is maintain in the code to track the final
- * state of the logging feature.
- * 
- * Setting AOCL_DTL_LOG_ENABLE = 0 will disable this feature
- * completely and it is not recommended.
- */
-#define AOCL_DTL_LOG_ENABLE         1
+/* Macro for dumping the log If the user wants to enable input logs he has to
+   enable this macro by making it to 1 else 0 */
+#define AOCL_DTL_LOG_ENABLE         0
 
 /* Select the trace level till which you want to log the data */
 /* By default it will log for all levels */