score: Remove _Internal_errors_What_happened

Users have access to the fatal error source and code though the fatal error
extension.  The user-specific fatal error handling should be done in statically
initialized fatal error handlers.  The _Internal_errors_What_happened was
updated after the fatal error extension. In addition, there was no API to get
the information stored in _Internal_errors_What_happened.  In SMP
configurations, this object could contain a mix of different fatal errors.
Remove this object to save some bytes of storage.

1 files changed, 1 insertions, 17 deletions

diff --git a/cpukit/include/rtems/score/interr.h b/cpukit/include/rtems/score/interr.h
index e5a0a62cf6..65cac29500 100644
--- a/cpukit/include/rtems/score/interr.h
+++ b/cpukit/include/rtems/score/interr.h
@@ -215,21 +215,6 @@ typedef enum {
 typedef CPU_Uint32ptr Internal_errors_t;
 
 /**
- *  This type holds the fatal error information.
- */
-typedef struct {
-  /** This is the source of the error. */
-  Internal_errors_Source  the_source;
-  /** This is the error code. */
-  Internal_errors_t       the_error;
-} Internal_errors_Information;
-
-/**
- *  When a fatal error occurs, the error information is stored here.
- */
-extern Internal_errors_Information _Internal_errors_What_happened;
-
-/**
  * @brief Initiates system termination.
  *
  * This routine is invoked when the application or the executive itself
@@ -253,8 +238,7 @@ extern Internal_errors_Information _Internal_errors_What_happened;
  * may install an initial extension that performs a system reset.  In this case
  * the non-initial extensions will be not called.
  *
- * Once all fatal handler executed the error information will be stored to
- * _Internal_errors_What_happened and the system state is set to
+ * Once all fatal handler executed the system state is set to
  * SYSTEM_STATE_TERMINATED.
  *
  * The final step is to call the CPU specific _CPU_Fatal_halt().