On 04.01.2024 22:41, Kinsey Moore wrote:
This is technically a false warning since rtems_interrupt_disable is a macro that expands to _ISR_Local_disable that expands to _CPU_ISR_Disable which assigns it a value, but it doesn't hurt anything, so it's OK to commit.Kinsey On Thu, Jan 4, 2024 at 12:54 PM <berndmoessne...@gmail.com> wrote: From: Bernd Moessner <berndmoessne...@gmail.com> --- rtemslwip/common/sys_arch.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rtemslwip/common/sys_arch.c b/rtemslwip/common/sys_arch.c index 2651c9c..b97404c 100644 --- a/rtemslwip/common/sys_arch.c +++ b/rtemslwip/common/sys_arch.c @@ -372,7 +372,7 @@ sys_request_irq(unsigned int irqnum, sys_irq_handler_t handler, sys_prot_t sys_arch_protect() { - sys_prot_t pval; + sys_prot_t pval = 0; #if RTEMS_SMP rtems_recursive_mutex_lock( &sys_arch_lock );-- 2.34.1_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Yes, I saw that it doesnt hurt. I get similar warnings from the RTEMS Kernel. However, I will have to "fix" this warnings as I am required to enable -Werror.
Bernd
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
