This is ok to push.
Unfortunate but this is the reality. A GCC 14 release is still future tense.
On Sat, Apr 13, 2024, 8:49 PM wrote:
> From: Chris Johns
>
> Change back to gcc-13 branch and a git version as gcc-13.2 does
> not build on MacOS 14.4. The fixes are on the gcc-13 release branch.
Thanks, it should be fixed.
Chris
On 13/4/2024 12:41 am, Heinz Junkes wrote:
> Common Name (CN)
> docs.rtems.org
> Organisation (O)
>
> Organisational Unit (OU)
>
> Issued By
> Common Name (CN)
> R3
> Organisation (O)
> Let's Encrypt
> Organisational Unit (OU)
>
> Validity Period
> Issued On
From: Chris Johns
Change back to gcc-13 branch and a git version as gcc-13.2 does
not build on MacOS 14.4. The fixes are on the gcc-13 release branch.
---
rtems/config/6/rtems-default.bset | 2 +-
rtems/config/tools/rtems-gcc-13-newlib-head.cfg | 6 +++---
2 files changed, 4
The clock from the ARM timer is derived from the system clock. This clock can
change dynamically e.g. if the system goes into reduced power or in low power
mode. Thus the clock speed adapts to the overall system performance
capabilities. For accurate timing it is recommended to use the system
On 13.04.24 12:13, Ning Yang wrote:
diff --git a/bsps/aarch64/raspberrypi/include/bsp/irq.h
b/bsps/aarch64/raspberrypi/include/bsp/irq.h
index 1ff6ae80de..f2dd2f6c14 100644
--- a/bsps/aarch64/raspberrypi/include/bsp/irq.h
+++ b/bsps/aarch64/raspberrypi/include/bsp/irq.h
@@ -9,6 +9,7 @@
/**
The clock from the ARM timer is derived from the system clock. This clock can
change dynamically e.g. if the system goes into reduced power or in low power
mode. Thus the clock speed adapts to the overall system performance
capabilities. For accurate timing it is recommended to use the system
