What is the effect of an RTX Tiny context switch (via specifying a non-zero TIMESHARING value in Conf_tny.A51) on non-reentrant functions? I would assume that functions documented as reentrant will be OK, but is it safe to assume all non-reentrant functions within the scope of a task will allocate their own non-overlayed segment? What about compiler-generated library calls...specifically floating point? Are these immune to a mid-process context switch invoked by RTX Tiny?