> On Sep 9, 2015, at 19:02 , Joel Sherrill <joel.sherr...@oarcorp.com> wrote: > > As Sebastian mentioned if you make the task stack accessible by only > a single stack, you have to be careful not to pass pointers to objects > on the stack into paths where they will be used by another task.
I’ve worked on multi-processor systems with this attribute and I think it’s a good option, stack was private and “cheap” in terms of overhead on a processor. If you use shared memory semantics you'll have portable code that works on multi-process (process, not processor) systems, it requires a little more design formalism up front. Peter ----------------- Peter Dufault HD Associates, Inc. Software and System Engineering _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
