Use of RTEMS_GLOBAL in non-multiprocessing configurations?

[Joel Sherrill]

On Mon, Jun 15, 2020 at 10:52 AM Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

> Hello,
>
> should the use of RTEMS_GLOBAL be an error in rtems_semaphore_create(),
> rtems_task_create(), rtems_message_queue_create(), and
> rtems_partition_create() if RTEMS was configured without multiprocessing
> enabled?
>

Based on the original use cases, I would say no. The idea was that you
could create
objects and attach to them to limit cohesion. The intention was to avoid
the use of
global variables for sharing object Ids.  If I offer a service via a
message queue
globally and my library/service is deployed in a non-MP configuration, it
should still
work. For tasks, that would imply events. For partitions, it just means the
memory is
available to "the system" which is a single processor.

--joel

>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20200615/7f2c6cb6/attachment.html>