You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Compiler warnings about deprecated [-Wvolatile] operations, feels like those shouldn't exist.
C:/Users/dougl/git/Webserver/ext/picoinf/ext/FreeRTOS-Kernel/portable/ThirdParty/GCC/RP2040/include/portmacro.h: In function 'void vPortRecursiveLock(uint32_t, spin_lock_t*, BaseType_t)':
C:/Users/dougl/git/Webserver/ext/picoinf/ext/FreeRTOS-Kernel/portable/ThirdParty/GCC/RP2040/include/portmacro.h:230:51: warning: '++' expression of 'volatile'-qualified type is deprecated [-Wvolatile]
230 | ucRecursionCountByLock[ ulLockNum ]++;
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
C:/Users/dougl/git/Webserver/ext/picoinf/ext/FreeRTOS-Kernel/portable/ThirdParty/GCC/RP2040/include/portmacro.h:244:50: warning: '--' expression of 'volatile'-qualified type is deprecated [-Wvolatile]
244 | if( !--ucRecursionCountByLock[ ulLockNum ] )
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
Describe the solution you'd like
I would like a clean build with -Wall, etc.
Describe alternatives you've considered
None.
How many devices will this feature impact?
Personal.
What are your project timelines?
Personal.
Additional context
I am upgrading to the pico-sdk 2.1.0, and part of that was guidance (in the 2.0.0 upgrade) to use this rpi-fork FreeRTOS-Kernel repo specifically. Previously I was using the original FreeRTOS-Kernel, and there were no compiler warnings on build.
I don't know what, if anything, is special about this fork, but I'd like to both follow guidance and have a clean build.
If I'm misunderstanding something please shout.
Thanks.
Doug
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Compiler warnings about deprecated [-Wvolatile] operations, feels like those shouldn't exist.
Describe the solution you'd like
I would like a clean build with -Wall, etc.
Describe alternatives you've considered
None.
How many devices will this feature impact?
Personal.
What are your project timelines?
Personal.
Additional context
I am upgrading to the pico-sdk 2.1.0, and part of that was guidance (in the 2.0.0 upgrade) to use this rpi-fork FreeRTOS-Kernel repo specifically. Previously I was using the original FreeRTOS-Kernel, and there were no compiler warnings on build.
I don't know what, if anything, is special about this fork, but I'd like to both follow guidance and have a clean build.
If I'm misunderstanding something please shout.
Thanks.
Doug
The text was updated successfully, but these errors were encountered: