Also add new build locations and include directories.
This renames 4 files to their original names that had no changes:
stm32u5xx_hal_msp.c ->
stm32u5xx_hal_msp_template.c
stm32u5xx_hal_timebase_rtc_wakeup.c ->
stm32u5xx_hal_timebase_rtc_wakeup_template.c
stm32u5xx_hal_timebase_tim.c ->
stm32u5xx_hal_timebase_tim_template.c
stm32u5xx_hal_timebase_rtc_alarm.c ->
stm32u5xx_hal_timebase_rtc_alarm_template.c
There is one file left behind that will be sorted out in the future:
stm32u5/hal/system_stm32u5xx.c
It comes from
07b6fedf4b/Projects/NUCLEO-U575ZI-Q/Applications/ThreadX/Tx_LowPower/Src/system_stm32u5xx.c
As per Christian on Discord.
These have now moved to:
contrib/bsps/arm/stm32h7/cmsis-device-h7
contrib/bsps/arm/stm32h7/stm32h7xx_hal_driver
Also add include directories to the build.
These changes are from:
cb78150d86
A comment was removed from the top of the file noting its modification no need
for this as the changes are in a separate commit now.
c20dc9c7aa added test code which included a cancellation cleanup
handler and a pthread body which were of the wrong prototype. With
GCC 15, this is now an error.
Incorrect format specifier: printf() adjusted to be clean on both 32
and 64 bit PowerPCs.
Defined but not used: Adjusted _ARCH_PPC64 ifdef's to properly
eliminate code not used on 64 bit PowerPCs.
The DBG_PRINTF() macro was using the GNU extension variadic macro
style. Switched to standard C style variadic macro, printk() so
safer for debug than printf(), and included needed files.
This adds support for the "vGetTLSAddr" GDB query which retrieves the
address of a TLS variable by offset from the beginning of the TLS memory
space for the given thread. This offset does not include the size of the
thread control block which is at the beginning of every TLS area as used
by RTEMS. Notably, the returned address is big-endian rather than the
little-endian typical with other responses.
This functionality does not include retrieval of addresses for TLS
variables hosted in loadable modules, only TLS variables in the host
binary.
According to the Posix specification:
Upon successful completion pthread_sigmask() shall return 0;
otherwise, it shall return the corresponding error number.
GCC warnings when comparing the starting addresses of two arrays when
using just the name of the array. Changes to use the address of
element 0 which resolved the warning.
On some BSP builds, the variable q was reported as used before
it was initialized. This is a false positive. The variable is now
initialized to NULL to prevent this.
This was warning about the FP context not being restored
when a thread is restarted. The current and long standing
execution path is through _Thread_Handler() which does restore
the FP context.
This function was static inline which means that it must compile
cleanly for all versions of C and C++. Newer C standards make it
an error to cast between incompatible function types. Moving this
function to cpu.c from cpu.h allows the C standard version required
to be narrowed from "whatever the user wants" to the one version
that is used to compile RTEMS.
