On 2014-04-09 08:17, Chris Johns wrote:
I propose to add a new requirement:
The non-SMP and SMP RTEMS Classic API should be ABI compatible.
I agree with this. I feel in this case the an error should be returned and the
user can then decide what to do.
Does mean we need to add the support deeper into the score ? I would assume
keeping the support out of the layer below the API should help keep the foot
print down on uni-processor builds.
Yes, behind the public ABI we should of course avoid overhead for non-SMP
systems. This is the case for the rtems_task_get/set_affinity() functions.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
rtems-devel mailing list
rtems-devel@rtems.org
http://www.rtems.org/mailman/listinfo/rtems-devel
