This appears to be because
rtems_configuration_get_user_multiprocessing_table() always returns a
non-NULL value when RTEMS_MULTIPROCESSING is defined. This must be a change
versus previous behavior.
Ryan and I noticed that the specific cases cited here appeared to be
wrapped in ifdef RTEMS_MULTIPROCESSING so didn't need to worry about it.
But something has changed that impacts public facing behavior.
--joel
On Mon, Mar 7, 2022 at 10:05 AM Ryan Long <ral...@oarcorp.com> wrote:
> Joel and I noticed these warnings when building the leon3 BSP with
> multiprocessing enabled. Joel thinks this means that something has
> changed around the multiprocessing configuration to generate these. Does
> anybody have an idea on how to fix these?
>
>
> In file included from ../../../cpukit/include/rtems.h:59,
> from ../../../cpukit/libmisc/stackchk/check.c:28:
> ../../../cpukit/libmisc/stackchk/check.c: In function
> 'Stack_check_report_blown_task':
> ../../../cpukit/include/rtems/config.h:492:5: warning: the address of
> '_MPCI_Configuration' will always evaluate as 'true' [-Waddress]
> 492 | ( &_MPCI_Configuration )
> | ^
> ../../../cpukit/libmisc/stackchk/check.c:281:9: note: in expansion of
> macro 'rtems_configuration_get_user_multiprocessing_table'
> 281 | if (rtems_configuration_get_user_multiprocessing_table()) {
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> ../../../cpukit/libmisc/monitor/mon-editor.c: In function
> 'rtems_monitor_command_read':
> ../../../cpukit/libmisc/monitor/mon-editor.c:503:7: warning: the address
> of '_MPCI_Configuration' will always evaluate as 'true' [-Waddress]
> 503 | if (!rtems_configuration_get_user_multiprocessing_table ())
>
> _______________________________________________
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
