Cleanup license text in Xtensa XCC and Xtensa ESP32 GCC ports.

Add SPXD license identifiers.

portable/ThirdParty/GCC/Xtensa_ESP32/include/xtensa_context.h

@@ -1,25 +1,33 @@
+/*
+ * FreeRTOS Kernel <DEVELOPMENT BRANCH>
+ * Copyright (C) 2006-2015 Cadence Design Systems, Inc.
+ * Copyright (C) 2021 Amazon.com, Inc. or its affiliates.  All Rights Reserved.
+ *
+ * SPDX-License-Identifier: MIT
+ *
+ * Permission is hereby granted, free of charge, to any person obtaining a copy of
+ * this software and associated documentation files (the "Software"), to deal in
+ * the Software without restriction, including without limitation the rights to
+ * use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+ * the Software, and to permit persons to whom the Software is furnished to do so,
+ * subject to the following conditions:
+ *
+ * The above copyright notice and this permission notice shall be included in all
+ * copies or substantial portions of the Software.
+ *
+ * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
+ * FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+ * COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+ * IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+ * CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+ *
+ * https://www.FreeRTOS.org
+ * https://github.com/FreeRTOS
+ *
+ */
+
 /*******************************************************************************
-Copyright (c) 2006-2015 Cadence Design Systems Inc.
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of this software and associated documentation files (the
-"Software"), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:
-
-The above copyright notice and this permission notice shall be included
-in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
-CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
-SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
---------------------------------------------------------------------------------
 
         XTENSA CONTEXT FRAMES AND MACROS FOR RTOS ASSEMBLER SOURCES
 
@@ -87,16 +95,16 @@ NOTE: The Xtensa architecture requires stack pointer alignment to 16 bytes.
   INTERRUPT/EXCEPTION STACK FRAME FOR A THREAD OR NESTED INTERRUPT
 
   A stack frame of this structure is allocated for any interrupt or exception.
-  It goes on the current stack. If the RTOS has a system stack for handling 
-  interrupts, every thread stack must allow space for just one interrupt stack 
+  It goes on the current stack. If the RTOS has a system stack for handling
+  interrupts, every thread stack must allow space for just one interrupt stack
   frame, then nested interrupt stack frames go on the system stack.
 
-  The frame includes basic registers (explicit) and "extra" registers introduced 
+  The frame includes basic registers (explicit) and "extra" registers introduced
   by user TIE or the use of the MAC16 option in the user's Xtensa config.
   The frame size is minimized by omitting regs not applicable to user's config.
 
   For Windowed ABI, this stack frame includes the interruptee's base save area,
-  another base save area to manage gcc nested functions, and a little temporary 
+  another base save area to manage gcc nested functions, and a little temporary
   space to help manage the spilling of the register windows.
 -------------------------------------------------------------------------------
 */
@@ -164,7 +172,7 @@ STRUCT_END(XtExcFrame)
 
 #else
 
-#define XT_STK_NEXT2            XT_STK_NEXT1   
+#define XT_STK_NEXT2            XT_STK_NEXT1
 
 #endif
 
@@ -181,12 +189,12 @@ STRUCT_END(XtExcFrame)
 -------------------------------------------------------------------------------
   SOLICITED STACK FRAME FOR A THREAD
 
-  A stack frame of this structure is allocated whenever a thread enters the 
+  A stack frame of this structure is allocated whenever a thread enters the
   RTOS kernel intentionally (and synchronously) to submit to thread scheduling.
   It goes on the current thread's stack.
 
   The solicited frame only includes registers that are required to be preserved
-  by the callee according to the compiler's ABI conventions, some space to save 
+  by the callee according to the compiler's ABI conventions, some space to save
   the return address for returning to the caller, and the caller's PS register.
 
   For Windowed ABI, this stack frame includes the caller's base save area.
@@ -194,7 +202,7 @@ STRUCT_END(XtExcFrame)
   Note on XT_SOL_EXIT field:
       It is necessary to distinguish a solicited from an interrupt stack frame.
       This field corresponds to XT_STK_EXIT in the interrupt stack frame and is
-      always at the same offset (0). It can be written with a code (usually 0) 
+      always at the same offset (0). It can be written with a code (usually 0)
       to distinguish a solicted frame from an interrupt frame. An RTOS port may
       opt to ignore this field if it has another way of distinguishing frames.
 -------------------------------------------------------------------------------
@@ -239,7 +247,7 @@ STRUCT_END(XtSolFrame)
   and the context switch of that co-processor is then peformed by the handler.
   Ownership represents which thread's state is currently in the co-processor.
 
-  Co-processors may not be used by interrupt or exception handlers. If an 
+  Co-processors may not be used by interrupt or exception handlers. If an
   co-processor instruction is executed by an interrupt or exception handler,
   the co-processor exception handler will trigger a kernel panic and freeze.
   This restriction is introduced to reduce the overhead of saving and restoring
@@ -250,7 +258,7 @@ STRUCT_END(XtSolFrame)
   such as in the thread control block or above the thread stack area. It need
   not be in the interrupt stack frame since interrupts don't use co-processors.
 
-  Along with the save area for each co-processor, two bitmasks with flags per 
+  Along with the save area for each co-processor, two bitmasks with flags per
   co-processor (laid out as in the CPENABLE reg) help manage context-switching
   co-processors as efficiently as possible:
 
@@ -266,10 +274,10 @@ STRUCT_END(XtSolFrame)
 
   XT_CPSTORED
     A bitmask with the same layout as CPENABLE, a bit per co-processor.
-    Indicates whether the state of each co-processor is saved in the state 
+    Indicates whether the state of each co-processor is saved in the state
     save area. When a thread enters the kernel, only the state of co-procs
-    still enabled in CPENABLE is saved. When the co-processor exception 
-    handler assigns ownership of a co-processor to a thread, it restores 
+    still enabled in CPENABLE is saved. When the co-processor exception
+    handler assigns ownership of a co-processor to a thread, it restores
     the saved state only if this bit is set, and clears this bit.
 
   XT_CP_CS_ST
@@ -352,7 +360,7 @@ STRUCT_END(XtSolFrame)
   For framed functions the frame is created and the return address saved at
   base of frame (Call0 ABI) or as determined by hardware (Windowed ABI).
   For frameless functions, there is no frame and return address remains in a0.
-  Note: Because CPP macros expand to a single line, macros requiring multi-line 
+  Note: Because CPP macros expand to a single line, macros requiring multi-line
   expansions are implemented as assembler macros.
 -------------------------------------------------------------------------------
 */
@@ -365,7 +373,7 @@ STRUCT_END(XtSolFrame)
     addi    sp, sp, -\size
     s32i    a0, sp, 0
     .endm
-  #define ENTRY0      
+  #define ENTRY0
   #define RET(sz)       ret1    sz
     .macro  ret1 size=0x10
     l32i    a0, sp, 0